Ah, that's the fact I feared :)
I perhaps can pass in parameters as 'args' as a work around and create the
_next hyperlink by converting args to anchor text.
I'm using browser history management so anchors have to be used 'eventually'.
On 18 Jun 2011, at 13:08, Anthony wrote:
> As I unders
As I understand it, browsers do not send anchors (i.e., "fragment
identifiers") to the server, so if a user clicks on
http://127.0.0.1:8000/init/default/account#Invite, the http request sent to
web2py will not include the "#Invite" part of the URL, and web2py will
therefore not be able to inclu
further investigation...
away from CAS...
in default.py:
def one():
redirect(URL(f='two', anchor='anchor987654321'))
def two():
redirect(URL(f='three'))
def three():
return dict(message='three!')
when I enter http://127.0.0.1:8000/init/default/one the function two()
is called and I'
an example:
if a user, not yet logged in, clicks the link
http://127.0.0.1:8000/init/default/account#Invite
they are asked to log in and then redirected to
http://127.0.0.1:8000/init/default/accountd
note that the hash (#Invite) is lost.
I'm using CAS in my app.
Has anyone encountered this?
4 matches
Mail list logo
