what is the difference between / and self.request.get('url' '/' ) ?
is it the full address? (Yes, I will try later this evening :-)
On Mar 5, 1:10 am, pedepy paul.ro...@gmail.com wrote:
yes i was gonna say, keeping track of the original URL in a logout
operation is probably not important, as
oh the only difference is that if I ever choose to pass the logout handler
an url 'value' it should be what it redirects it to, otherwise default to
'/'
for instance, www.mysite.com/logout?url=/something it will redirect to
/something .. thats probably more useful in login situations though where
Cool, that makes sense.
Thank you again.
On 6 Mrz., 01:30, Paul Roy paul.ro...@gmail.com wrote:
oh the only difference is that if I ever choose to pass the logout handler
an url 'value' it should be what it redirects it to, otherwise default to
'/'
for
yep well turns out this is exactly what im doing. but i dont see this
as generating a blank page. i have to try out the code i suggested
yesterday.
and i did make it home, thx :)
Sent from my iPhone
On 09-03-04, at 01:28, OliWeiD oliver.weimar.dr...@googlemail.com
wrote:
Well, I've
Hi Paul,
after multiple trials I found a way which is working:
1) as link I'm using now /logout
2) the following handler is answering to it (typical stuff in app.yaml
and wsgi application)
class LogoutHelper(webapp.RequestHandler):
def get(self):
usr = users.get_current_user()
yes i was gonna say, keeping track of the original URL in a logout
operation is probably not important, as you most likely want to simply
redirect to home page. (this can also make the user more 'secure' that
his session has indeed been properly terminated if its important to
your app)..
here's
perhaps, instead of using the users' method directly, create a logout
handler where you perform the necessary operations before fowarding to
the logout uri.
the tricky part is keeping track of the original uri. the way i do it,
is to pass it as a request argument. you could maybe subclass
