RE: [Zope] Zope Requests - POST vs. GET
[Andreas Jung]
--On Montag, 15. Dezember 2003 16:05 Uhr +0100 Tino Wildenhain <tino@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
Hi Tom, Passin, Tom wrote:
[Andreas Jung]
--On Montag, 15. Dezember 2003 16:05 Uhr +0100 Tino Wildenhain <tino@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.
The login page is the same for every article. So it cannot contain the destination URL. Of course one had to copy the QUERY parameters into a hidden form field. Which is also next to ugly.
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.
I dont think so. Its just a hindering decision to implement it this way. Better approach would have been to implement a GET and a POST namespace in REQUEST as well as mirroring the variables into Form as they are now. After all, a QUERY string in a Post URL is just valid information. I really cant see why Zope does not let us access it. And I'm very into standards. Regards Tino
participants (2)
-
Passin, Tom -
Tino Wildenhain