tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Bremford" <>
Subject RE: page has moved messages...
Date Fri, 04 Aug 2000 11:35:47 GMT
Just to follow up my own message :-)

Section 10.3.3 of the HTTP/1.1 spec says:

   If the 302 status code is received in response to a request other
   than GET or HEAD, the user agent MUST NOT automatically redirect the
   request unless it can be confirmed by the user, since this might
   change the conditions under which the request was issued.

I assume you're using a POST on the form. Switch it to GET and it should
work fine.

Cheers... Mike

-----Original Message-----
From: Mike Bremford []
Sent: 04 August 2000 12:21
Subject: RE: page has moved messages...

Hi Bill

Sounds like you're seeing the message that normally goes with a 302 return
code (temporary redirect). I can't think what would cause this off hand, but
it could be some sort of browser oddity with caching. Which browser are you

You might find that the browser is getting confused becuase you're sending a
302 code (to indicate that the page has moved somewhere else), but saying
it's moved to itself. Try tacking a "?" followed by a random number at the
end of the URL, or setting "Pragma: no-cache" or an expiry date in the past.

The way I would approach this is to see exactly what headers are being
passed to your browser - if in doubt, read the HTTP/1.1 spec
( and "telnet localhost 80".
Incidentally, unlike most RFCs this one can be understood by mere mortals
and is worth a read.

Good Luck

Cheers... Mike

-----Original Message-----
From: $Bill Dossett []
Sent: 04 August 2000 12:07
Subject: page has moved messages...


I've got a form that submits and update to a database,
then calls itself to display the data again so the user
can see his changes and make further updates... the
problem is that when I call the form, directly  after
the update, the mesages, "this page as moved to here"
with here being a hyperlink to the same page as
I have called...  The URL is correct in the browser
window and the requested URL is correct in the jasper
log, but I still get this message and can't figure out
why because as far as I can tell, all the paths and
stuff is corrrect....  the bulk of the code is produced
by macromedia ultradev.  Cool product, it writes the
code and you get to fix it :-)  anyway, I've picked
my way through all of the code and for once I think
it's right.. maybe,  any ideas on what I should look



View raw message