> -----Original Message-----
> From: Graham Leggett [mailto:[EMAIL PROTECTED]
> Sent: Saturday, April 28, 2001 6:48 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Keepalive issues
>
>
> Nathan Lutchansky wrote:
>
> > Thus, until I get around to porting mod_roaming to Apache
> 2.0, I resubmit
> > my request for an HTTP/1.0-option for mod_proxy. :-) -Nathan
>
> Doing this is dangerous - because then there is no point in fixing
> problems with HTTP/1.1 and the proxy. The HTTP/1.1 protocol is
> backwardly compatible with HTTP/1.0 - if it doesn't work, it's because
> something is broken and should be fixed.
>
I would like to also go forward with a HTTP/1.0 proxy for the reasons graham
mentioned (ie something is broken), unfortunatly in some cases we can't get
it fixed in a timely manner, and we don't have the code to make the changes
ourselves.
(BEA Weblogic 5.1 has a problem with HTTP/1.1 and keepalives, which should be
fixed in june they say)
so I face 2 options
a) modify the code to hard code 1.0
b) force the client to 1.0 (not sure if this works, as the code looks
like
it is hard coded to send 1.1 requests)
..ian
> Essentially before reverting to HTTP/1.0, first try switching
> Keepalives
> off on the proxy server and see if that makes a difference. The proxy
> will only use a backend-proxy Keepalive if a browser-proxy
> Keepalive is
> currently active. This will at least reduce the range of the problems,
> and make things easier to track down.
>
> Regards,
> Graham
> --
> -----------------------------------------
> [EMAIL PROTECTED] "There's a moon
> over Bourbon Street
> tonight..."
>
