How strange to find this conversation when I was dealing with this problem just last night. I often find I need to let my user click on a link to a new page in my app (e.g. to add a new item to a database) and then come back to the previous page (e.g. to use that new item in some way).
I've been using 'session.jump_back' as a variable to store the return URL so that the user can easily come back. Something like "if session.jump_back: redirect(session.jump_back)". In this case, proxies don't matter because I'm providing exactly the same URL that I expose to everyone by loading jump_back with URL(...). My simplistic approach has been working OK, but now I need a two-stage "jump_back". I'm thinking of making the jump_back variable like a stack, where the latest URL is prepended onto the string with some distinctive separator character, then when the jump is exercised a portion of the URL is "consumed" and discarded (i.e. popped from the stack). I don't know if any of this makes sense from a web design standpoint. I admit to being an experienced programmer who is a total newbie at doing websites. I can do lots of things in software but many of them would not be a good direction. This may be one... -- Joe B. On Apr 29, 9:23 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > no because web2py does not know what the full url is from the > prospective of the client. For example there may be one of multiple > proxies in between. This is a major problem. This is what causes some > problems to CAS users. > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
