As far as putting the ID into the url, I would suggest not. Even though the ID is secure and anonymous, django's urls allow for much better ways to determine a user and put them on a page. What is your purpose for using the ID in the URL?
On Wednesday, July 6, 2016 at 10:09:59 AM UTC-4, davidt wrote: > > I am looking for advice with regard to the following: > > I have a model which has as part of the structure these two fields > > job_id = models.AutoField(primary_key=True,) > job_reference = job_id = ShortUUIDField() > > My question is if I include the job_id in the url, which is public facing > then it is easy to guess the rest of the urls within the site. > Beacuse there are a number of items that will have the same url structure, > and are posted on the same day, using the id is what makes them unique. > > My questions are is this right way to proceed or is there a better > alternative? > > Thanks in advance > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/d39d267b-cdfc-45e8-9065-2c8521a8213f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
