Frawls wrote:
[color=blue]
> Hi
>
>
> Can any one give me some help with this problem please?
>
>
> Here is the scenario:
>
>
> A user submits page 1 which is a web form.
>
>
> After the form has been submitted they are (redirected) onto the next
> page, page 2.
>
>
> The user then clicks back on the browser.
>
>
> They are now back in page 1
>
>
> If the user clicks the continue button on page 1 this time the page
> just reloads and the user has to click submit again to get to page 2.[/color]
What is the "continue" button?
[color=blue]
> In other words after clicking the back button the user has to submit
> the form twice. (the first time it does not get submitted the page
> just
>
> reloads)
>
>
> Is this a known issue? Can anyone tell me what is causing it and how
> to
>
> rectify or fix it??[/color]
I'm not sure I understand your problem, but to me it seems as though
you've just discovered redirect-after-post. What happens is that in the
browser history, only the final request/response of a redirect chain is
saved.
In your case, it looks like this:
POST /p1.aspx --> 302 Found Location: /p2.aspx
GET /p2.aspx --> 200 OK
The browser only saves the last GET in its history. Thus, the POST is
never resubmitted by the browser when pressing refresh or back, which
is the reason why this pattern is actually quite useful ;-)
Cheers,
--
http://www.joergjooss.de
mailto:news-reply@joergjooss.de