[Zope] Zope Requests - POST vs. GET

Passin, Tom tpassin at mitretek.org
Mon Dec 15 11:04:13 EST 2003


[Andreas Jung]
> --On Montag, 15. Dezember 2003 16:05 Uhr +0100 Tino Wildenhain 
> <tino at wildenhain.de> wrote:
> 
> > Maybe next example makes it more transparent:
> >
> > you make a link published in a  e-mail which provides 
> information of 
> > an article in a shop referenced by QUERY-String, of course.
> >
> > In the resulting page there is the option to log in
> > first - of course with POST.
> >
> 
> ok, thanks for pointing this out :-)

But in this example, the uri + query string came from the email and
would have beend sent using a GET, while the login would have been done
using a POST with no need for the query string parameters.  The login
page should contain the destination uri, and should not depend on
getting them from a query parameter copied from a previous page.

So this example does not argue strongly for a combination of GET and
POST. IMHO, the two should not be mixed because they have different
semantics.  A POST is intended for sending information to the server to
apply to the resource designated by the current uri, a GET is for
requesting a new page designated by the uri.  I think it is wise to keep
them separated.

Cheers,

Tom P



More information about the Zope mailing list