I'm starting to update Graham's HTTP/1.1 patch for 1.3.19(?) and get it up somewhere at apache.org for people to test and later use.. That should let people have the upgrade option sooner than 2.0 will be out.
On Wednesday, February 21, 2001, at 01:11 PM, [EMAIL PROTECTED] wrote: > Excuse me for butting in here, but I've been tracking down problems in > IE4-5.5 caching pages that they shouldn't when using ProxyPass & > ProxyPassReverse. Reading all sorts of posts in Deja.com (now google) I see > that IE is extremely picky, and really only pays attention to the HTTP/1.1 > cache-control & expires information. I captured the headers IE we seeing and > noticed that it's an HTTP/1.o header with the proper controls. So, IE > ignores it. > > Since proxy_http.c always issues HTTP/1.0 in it's proxy header (at least in > 1.3.17, around line 469) using a static string, I tried a real Kludge of a > patch. I hard coded it to HTTP/1.1 and IT WORKS. Who knows how many browsers > this will break, so I don't dare release this thought into the Wild. > > Is the mod_proxy development going to be able to get mod_proxy up to 1.1, or > at least test to see that not too much gets broken? Then ideal solution is > to pass the header properly from the original Server as to version, etc. > > Thanks for your time. > > S.W. > [EMAIL PROTECTED] > > Chuck Murcko Topsail Group http://www.topsail.org/
