Re: URL design

I can test this right now but based in my experience in re I think could be like this url(r'^(?P[a-zA-Z0-9_\-]+)/(?P[a-zA-Z0-9_\-]+)/(?P([a-zA-Z0-9_\-]+)/){7})$', views.item_list) Be worry with / in views El viernes, 3 de junio de 2016, Горобец Дмитрий escribió: > Hello, guys. > I have the foll

Re: URL design - why the trailing slash?

Nope, no caveat there. You'r perfectly free to design your own URLs as you like. Ultimately, means you can also have a conflicting situation where you decide you don't want to have a trailing `/` but you include URLs from a 3p django application that do. On Jan 28, 1:54 am, Brett Thomas wrote: >

Re: URL design - why the trailing slash?

On Jan 28, 12:54 am, Brett Thomas wrote: > Most of the URLConf examples I run across use a trailing slash on all > URLs:www.example.com/profile/ > > I'm not sure why, but I don't like this. I think it looks nicer > without:www.example.com/profile > > Are there any performance or security reasons

Re: URL design - why the trailing slash?

On Jan 28, 11:54 am, Brett Thomas wrote: > Most of the URLConf examples I run across use a trailing slash on all > URLs:www.example.com/profile/ > > I'm not sure why, but I don't like this. I think it looks nicer > without:www.example.com/profile > > Are there any performance or security reaso

Re: URL design - why the trailing slash?

Hi, On Thu, Jan 28, 2010 at 8:54 AM, Brett Thomas wrote: > Most of the URLConf examples I run across use a trailing slash on all URLs: > www.example.com/profile/ > > I'm not sure why, but I don't like this. I think it looks nicer without: > www.example.com/profile I believe that it is just a mat

Re: URL design - why the trailing slash?

Brett Thomas wrote: Most of the URLConf examples I run across use a trailing slash on all URLs: www.example.com/profile/ I'm not sure why, but I don't like this. I think it looks nicer without: www.example.com/profile Are the

Re: URL design for security?

Right: an integer id is not sensitive information. The problem arises (as in your original example), when a malicious user can edit the URL to change the id to another that he is not allowed to see, and your application lets him see it. It's that last part you have to prevent. After using th

Re: URL design for security?

On 7/14/07, Rogelio <[EMAIL PROTECTED]> wrote: > yet. I guess I was > thinking that even if the user was logged in, the URL still would be > showing potentially > sensitive info. I was thinking maybe I needed to create some random > sequence of > letters/numbers, store that in a model field and

Re: URL design for security?

Thanks for the replies. No, I haven't incorporated authentication yet. I guess I was thinking that even if the user was logged in, the URL still would be showing potentially sensitive info. I was thinking maybe I needed to create some random sequence of letters/numbers, store that in a model fi

Re: URL design for security?

> So my newbie question is: Is there a way a better way to design/ > obfuscate the URL scheme when dealing with sensitive information? I > know once I get some sort of authentication in place that will help, > but the idea of showing sensitive info in a URL still has me > concerned. The simpl

Re: URL design for security?

Are you using authentication? It's better to handle security policies in your application instead of hiding informations in URLs Have a look at http://www.djangoproject.com/documentation/authentication Bye, Massimo --~--~-~--~~~---~--~~ You received this message