Re: Proxy-Connection: close header
Adrian Sutton wrote: Do you have any idea how to make squid use that header? I don't think we're doing anything special to make it happen. Here are the headers from a couple of typical transaction, with a few host names slightly obscured. This is using my own Java-based caching code on top of httpclient alpha 1. (I'm starting to upgrade to the latest version now). Try to fetch a resource from a machine the Squid proxy doesn't have access to: 16:49:30:311 HTTP request headers for jack.vxml: Host: privatemachine.bevocal.com User-Agent: BeVocal/2.4 VoiceXML/2.0 BVPlatform/1.8.0.6 16:49:30:326 HTTP response headers for jack.vxml: HTTP/1.0 503 Service Unavailable Proxy-Connection: close Expires: Thu, 20 Feb 2003 00:49:31 GMT Date: Thu, 20 Feb 2003 00:49:31 GMT Server: squid/2.5.STABLE1 Content-Length: 1285 X-Squid-Error: ERR_DNS_FAIL 0 Content-Type: text/html X-Cache: MISS from proxy01.x.bevocal.com Mime-Version: 1.0 Fetch from a resource it *does* have access to 16:51:52:537 HTTP request headers for jack.vxml: Host: www.somewhere.com User-Agent: BeVocal/2.4 VoiceXML/2.0 BVPlatform/1.8.0.6 16:51:52:662 HTTP response headers for jack.vxml: HTTP/1.0 200 OK Proxy-Connection: close Accept-Ranges: bytes Date: Thu, 20 Feb 2003 00:47:55 GMT Server: Apache/1.3.22 (Unix) (Red-Hat/Linux) mod_jk/1.2.0 mod_perl/1.24_01 PHP/4.2.2 FrontPage/5.0.2 mod_ssl/2.8.5 OpenSSL/0.9.6b Content-Length: 14853 ETag: "19f7e5-3a05-3e3b1965" Last-Modified: Sat, 01 Feb 2003 00:48:37 GMT Content-Type: text/plain X-Cache: MISS from proxy01.x.bevocal.com Fetch the same resource again a minute or two later... 16:56:31:115 HTTP request headers for jack.vxml: Host: www.zenstarstudio.com User-Agent: BeVocal/2.4 VoiceXML/2.0 BVPlatform/1.8.0.6 16:56:31:115 HTTP response headers for jack.vxml: HTTP/1.0 200 OK Proxy-Connection: close Accept-Ranges: bytes Date: Thu, 20 Feb 2003 00:47:55 GMT Server: Apache/1.3.22 (Unix) (Red-Hat/Linux) mod_jk/1.2.0 mod_perl/1.24_01 PHP/4.2.2 FrontPage/5.0.2 mod_ssl/2.8.5 OpenSSL/0.9.6b Content-Length: 14853 ETag: "19f7e5-3a05-3e3b1965" Last-Modified: Sat, 01 Feb 2003 00:48:37 GMT Age: 517 Content-Type: text/plain X-Cache: HIT from from proxy01.x.bevocal.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Proxy-Connection: close header
Ah really! Excellent, I'd love to have a local test machine set up that does it. Currently I'm in the process of uploading a new build of our entire product so that an external client can tell me whether or not the problem is fully resolved. I do a pretty good proxy impersonation with netcat but there are distinct limits to that approach. :) Do you have any idea how to make squid use that header? Adrian Sutton, Software Engineer Ephox Corporation www.ephox.com -Original Message- From: Laura Werner [mailto:[EMAIL PROTECTED]] Sent: Thursday, 20 February 2003 7:47 AM To: Commons HttpClient Project Subject: Re: Proxy-Connection: close header Adrian Sutton wrote: >Just run into a non-standards compliance problem with IIS proxies in certain >configurations. At times instead of returning a "Connection: close" header, >it returns a "Proxy-connection: close" header. > For what it's worth, I've noticed that Squid sometimes uses a Proxy-Connection header as well. So whatever patch you come up with will probably be useful for more than just IIS. Laura Werner BeVocal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proxy-Connection: close header
Adrian Sutton wrote: Just run into a non-standards compliance problem with IIS proxies in certain configurations. At times instead of returning a "Connection: close" header, it returns a "Proxy-connection: close" header. For what it's worth, I've noticed that Squid sometimes uses a Proxy-Connection header as well. So whatever patch you come up with will probably be useful for more than just IIS. Laura Werner BeVocal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Proxy-Connection: close header
Hi all, Just run into a non-standards compliance problem with IIS proxies in certain configurations. At times instead of returning a "Connection: close" header, it returns a "Proxy-connection: close" header. HttpClient misses this notification and throws an exception when it suddenly discovers the connection was closed. With anything but NTLM authentication I imagine that this would work, but HttpClient runs out of retry attempts when using NTLM. The solution in the older codebase I'm using is to just add a check for Proxy-connection: close in HttpMethodBase.shouldCloseConnection(). I'm sure there's a similar function in the updated code. I'll look into it further and hopefully come up with a patch for discussion late this afternoon. If anyone has comments or a better solution I'd love to hear about it though. Adrian Sutton, Software Engineer Ephox Corporation www.ephox.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
