I'm working on a JSP shopping cart implementation, and am having a problem
getting a desired behavior. Here's what happens with my shopping cart:
-- my cart --
(1) User is viewing the cart,
(2) User changes the quantity of item(s) in the cart via a form
(METHOD=post), and submits.
(3) Quantity
cation and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Lastname Firstname
Sent: Thursday, June 10, 1999 11:17 AM
To: [EMAIL PROTECTED]
Subject: Re: POST and browser behavior
I would also be interested in an answer for this. Internet Explorer (IE)
4.01 experiences the same problem wh
Anyways, my advice still stands - use GET if you can.
Unfortunately, GET is not appropriate all the time. In the case of a
shopping cart application, using get would cause the form to be re-executed
automatically, which defeats the purpose (see my original post). Somehow,
amazon is managing to
and browser behavior
Anyways, my advice still stands - use GET if you can.
Unfortunately, GET is not appropriate all the time. In the case of a
shopping cart application, using get would cause the form to be re-executed
automatically, which defeats the purpose (see my original post). Somehow
5.
[EMAIL PROTECTED] on 06/10/99 12:24:44 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:(bcc: Glen C. Hawkins/Users/Skyway)
Subject: Re: POST and browser behavior
Anyways, my advice still stands - use GET if you can.
Unfortunately, GET is not appropriate all
-Original Message-
From: Chris Fesler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 10, 1999 03:25 PM
To: [EMAIL PROTECTED]
Subject: Re: POST and browser behavior
Anyways, my advice still stands - use GET if you can.
Unfortunately, GET is not appropriate all the time. In the case
Some ideas that might be useful.
1. Use POST but then do a redirect.
You post to a page that updates the state (say add something to the basket)
and then redirect to a page which display the new state (contents of the
basket). This way the user can hit reload and it doesn't reapply the post.
Separator _
Subject: Re: POST and browser behavior
Author: Taggart Gorman [EMAIL PROTECTED] at Internet
Date:6/10/99 11:57 AM
As far as I can tell, this is a "design decision" on Microsoft's part. My
guess is that they felt that POSTing a form is usually done for som
GET does not have a body ( all the data has to be send in the URL)
POST has a body which contains the data in URL-encoded format.
GET appends the form variables string to URL using (?)
POST send the form string data as request body (check HTTP protocol spec)
its easy to test web application if
Thanks!
c
Ed
Livin' La Vida Loca
-Original Message-
From: Chris Fesler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 10, 1999 03:25 PM
To: [EMAIL PROTECTED]
Subject: Re: POST and browser behavior
Anyways, my advice still stands - use GET if you can.
Bob Foster wrote:
The original "problem" was that the user set a quantity and did a
POST. The
user-visible result of the POST was evidently to redisplay the same page.
Then the user changed a quantity and instead of hitting the submit button
again, hit the back button.
Not exactly -- the
11 matches
Mail list logo
