Re: LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-12 Thread Carl Meyer
Hi Russ, On Jul 10, 8:24 am, Russell Keith-Magee wrote: > On Sat, Jul 10, 2010 at 12:49 AM, Carl Meyer wrote: > > Wouldn't it be most sensible to treat the URL mount point similarly to > > hostname, since they are really just two pieces of the

Re: LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-11 Thread SmileyChris
On Jul 11, 12:14 am, Russell Keith-Magee wrote: > > So you can't put reverse now in settings.py unless there is some > > late-binding construct, like > > > LOGIN_URL = RevLink('accounts:login', account_type='user') > > You shouldn't have to put reverse() calls into

Re: LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-10 Thread Alex Gaynor
On Sat, Jul 10, 2010 at 7:24 AM, Russell Keith-Magee wrote: > On Sat, Jul 10, 2010 at 12:49 AM, Carl Meyer wrote: >> On Jul 7, 7:11 pm, Graham Dumpleton >> wrote: >> [snip] >>> web application, to be a well behaved

Re: LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-10 Thread Russell Keith-Magee
On Sat, Jul 10, 2010 at 12:49 AM, Carl Meyer wrote: > On Jul 7, 7:11 pm, Graham Dumpleton > wrote: > [snip] >> web application, to be a well behaved WSGI citizen, should honour >> SCRIPT_NAME setting as supplied by the server, and ensure that

Re: LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-10 Thread Russell Keith-Magee
On Sat, Jul 10, 2010 at 12:19 AM, burc...@gmail.com wrote: > Tom, > > HTTP_HOST and other don't solve the multiple-host deployment, and it > is a solution you can do by yourself if you need. > > I'd like to see better solution: ability to make reverse work for such URLs. > I

Re: LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-09 Thread Carl Meyer
On Jul 7, 7:11 pm, Graham Dumpleton wrote: [snip] > web application, to be a well behaved WSGI citizen, should honour > SCRIPT_NAME setting as supplied by the server, and ensure that ways > are provided such that everything in the users code, including > configuration,

Re: LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-09 Thread burc...@gmail.com
Tom, HTTP_HOST and other don't solve the multiple-host deployment, and it is a solution you can do by yourself if you need. I'd like to see better solution: ability to make reverse work for such URLs. I think, currently the problem is in the binding time: The load order is typically the

Re: LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-09 Thread Tom Evans
On Thu, Jul 8, 2010 at 3:40 PM, Russell Keith-Magee wrote: > Personally, I see this as a case of explicit vs implicit. > > As currently defined, LOGIN_URL points to the login URL. Period. > > Under the proposed patch, the onus is on every possible script to > ensure that

Re: LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-08 Thread Russell Keith-Magee
On Thu, Jul 8, 2010 at 7:11 AM, Graham Dumpleton wrote: > Can the following issue be revisited. > >  http://code.djangoproject.com/ticket/8906 > > Conversation about it at: > >  

LOGIN_URL, LOGOUT_URL, LOGIN_REDIRECT_URL and SCRIPT_NAME.

2010-07-07 Thread Graham Dumpleton
Can the following issue be revisited. http://code.djangoproject.com/ticket/8906 Conversation about it at: http://groups.google.com/group/django-users/browse_frm/thread/c457599caab6e87d/b70e1f56ad38f4cb This is another of those issues where Django isn't being particular friendly to people