Hi All,
I'm trying to set things up so that my login form uses SSL to protect the user's password in transit. Basically, the behaviour I'm after is as follows: 1) Unauthenticated user requests http://site/private/ 2) They're redirected to http://site/login/ 3) They submit their details securely to https://site/login/ 4) This establishes the login and redirects to http://site/private/ However, conrtib.auth seems to actively not want me doing things this way. I tried putting the entire URL into the 'next' parameter to the login view, but it checks for non-local URLs and simply ignores them. Does anyone have advice for setting up this little redirect dance? Or is Django trying to steer me towards a better way of securing logins that I'm just not aware of? Thanks, Ryan -- Ryan Kelly http://www.rfk.id.au | This message is digitally signed. Please visit [email protected] | http://www.rfk.id.au/ramblings/gpg/ for details
signature.asc
Description: This is a digitally signed message part
