It responds with 303 status code and returns new location of the resource,
so the browser will issue GET request to the new location.
On Tuesday, April 23, 2013 11:08:01 PM UTC+4, NSC wrote:
>
> OK, I'm having some confusion with seeother(), likely because 95% of my
> application is ajax and my brain is locked into that mindset. Can someone
> clarify if the following presumption is true?
>
> I observe that for a request, 'seeother' simply a) resets the response
> buffer/headers and b) delivers a different resource in it's place. So
> basically for example, you hit /foo, which has code that does a
> seeother("/bar"). The response delivered to the client is identical as if
> they had originally requested /bar.
>
> Is this observation correct?
>
> Thanks!
> S
>
--
You received this message because you are subscribed to the Google Groups
"web.py" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to webpy+unsubscr...@googlegroups.com.
To post to this group, send email to webpy@googlegroups.com.
Visit this group at http://groups.google.com/group/webpy?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
