> Thanks for the fantastic insight into the browser issues with 307 > redirects. I'll explore this a bit further and see which route I want > to take.
I believe contrib.auth uses a 302 redirection which doesn't pass along the POST data. > Given that the form in question is simply a button that says "Join > network," I may be inclined to just let the user login, come back to > the page and submit the form again. An annoying experience (IMHO), but > one that eliminates all this hassle. One more option that occurs to me is that you can stash all of the POSTed variables into a session-store with a hash key, redirect with some sort of "load POST variables from this hash-key" GET page, and then when the login is done, redirect to your form, loading the contents from the session-store based on the key you pass in. -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
