Re: append_domain & squid_hno

The problem is probably the redirect, which causes the frames to be in
different JavaScript security contexts.

As a workaround, instead of using append_domain, use a redirector which
returns a browser redirect when the short name is requested.

#!/usr/bin/perl -p
BEGIN { $|=1; }
s%http://serv(/|$)%301:http://serv.foo.com/%

/Henrik

Charles Bruneteau wrote:
>
> Hi,
>
> Using squid-2.2.STABLE5_hno.20000202.snapshot i 've come into a strange problem.
>
> The squid configuration is very simple :
> - always direct all
> - append_domain foo.com
>
> The application is frame based; a frame is loaded, and then should force parent
> frames to be reloaded (javascript parent.left.location etc.). This dosen't works
> using a not qualified server name with hno.20000202 squid (it's ok with a stock
> 2.2stable5).
>
> Client request :
>
> GET /base? HTTP/1.1
> host: serv
>
> Then the squid request :
>
> GET /base? HTTP/1.0
> host: serv.foo.com
>
> That is the server name is modified. (a stock 2.2stable5 would ask for the host
> 'serv' without the appended domain)
>
> The web server ask for a redirection :
>
> HTTP/1.1 302 Found
> Server: Lotus-Domino
> Date: Fri, 10 Nov 2000 11:41:25 GMT
> Location: http://serv.foo.com/C12566EB003D0E81/All?
> Connection: close
> Content-Type: text/html
>
> And Then the client asks for
> GET /C12566EB003D0E81/All? HTTP/1.1
> host: serv.foo.com
>
> This object contains the 'parent.*.location' references, but the parent frames
> are not reloaded.
>
> Seems to me that with the new url (server with appended domain) the parent
> frames may no longer be changed.
>
> My guess is that squid should not modify the host header.
>
> Do you have a clue ?
>
> Regards,
>
> Charles Bruneteau

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html