W3C home > Mailing lists > Public > www-talk@w3.org > November to December 2001

Updating browser ID of POST-returned page

From: Parenti, Mark <MParenti@Pirus.com>
Date: Thu, 15 Nov 2001 19:49:15 -0500
Message-Id: <200111160049.TAA01988@tux.w3.org>
To: "'www-talk@w3.org'" <www-talk@w3.org>
In our application, a user POSTs a page using a submit button. The page
returned from the POST reflects the results of the POST. Pretty basic stuff.
We need the returned page to be identified as itself in the browser.
Currently, it gets identified as the same page as the POST. To explain:

The browser displays page1.html.
The user causes page1.html to be sent via POST by hitting a submit button.
The server returns page2.html.

At this point, the browser still identifies the new page as "page1.html". We
use Javascript to generate page-specific links (a link to a help page, for
example). In this case, the Javascript will generate a call to display the
help for page1.html instead of page2.html.

I have tried various combinations of return status (201, 301, 307) and
"Location" and "Content-Location" headers, to no avail. If I return a "307"
status, the browser does identify the page as "page2.html", but then tries
to reload the page. Since the page is dynamically generated, the reload
doesn't work.

This happens with both IE (5.x and 6.x) and Netscape (6.1).

Any ideas as to how I can get the browser to identify the returned page as
"page2.html" without trying to reload it. The HTTP spec seems to indicate
that returning a "307" should do this, but the browsers still try to reload
...

Thanks,

Mark


-----------------------------------------------------------------------
Mark Parenti
Member of Technical Staff

Pirus Networks, 43 Nagog Park Acton, MA, 01720
e-mail: mparenti@pirus.com. tel: (978) 206-9161
Received on Thursday, 15 November 2001 19:49:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:27 GMT