I agree. ick. We did that until the UAT people worried about browsers with
no javascript. So then we sent a meta refresh tag:

<meta http-equiv="refresh" content="0; url=/yadda" />

but now Mozilla allows you to disable that, too. :)


Good idea with the host header, but I like general solutions. my app server
is currently down, but I wonder if the getRequestURI() method returns the
original url? Maybe we could make a java.net.URL object to parse out the
host and port?

-----Original Message-----
From: Nelson, Laird [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 4:45 PM
To: 'Struts Users Mailing List'
Subject: RE: [Unverified Sender] RE: [OT] response.sendRedirect with
proxy servers


> -----Original Message-----
> From: Nelson, Laird [mailto:[EMAIL PROTECTED]
> send back a
> tiny response that contains a Javascript payload that 
> instructs the browser
> to replace its location with the correct URL (relative).

The other thing I thought of: perhaps there's some Apache module you could
write (or one that exists already) to add the host and port and other
original protocol information as an X-Header.  Then you could see if those
headers are present in your webapp code, and if so, construct the proper
URL.

Hacking frenetically,
Laird

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to