Yes, that makes sense- thanks
On Dec 21, 10:13 pm, Anthony <abasta...@gmail.com> wrote:
> Note, browsers don't send fragment identifiers to the server, so web2py has
> no control over this. As far as I know, this is standard behavior for most
> browsers. It actually makes sense when you think about the meaning of a 30x
> redirect -- the server is saying that the resource requested can be found
> at a different URL, so the browser assumes the original fragment identifier
> can simply be applied to the new URL to find the fragment within the
> resource. Of course, in many cases, we're redirecting to a different
> page/resource, so it seems odd in those cases.
>
> Anthony
>
>
>
>
>
>
>
> On Wednesday, December 21, 2011 9:45:21 PM UTC-5, Yarin wrote:
>
> > I've noticed that when redirecting from a url with hash fragment ids
> > in the url, the fragment ids persist to the new url. This does not
> > seem right- for instance, when submitting a form on a screen with a
> > fragment id, the thank-you page gets the same url fragment.
>
> > Consider two simple pages:
>
> > def hello():
> > redirect(URL('goodbye'))
> > return dict(message='hello')
>
> > def goodbye():
> > return dict(message='goodbye')
>
> > /default/hello#there -> redirects to
> > /default/goodbye#there
