Return-Path: Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@www.apache.org Received: (qmail 47582 invoked from network); 12 Jan 2004 14:13:23 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 12 Jan 2004 14:13:23 -0000 Received: (qmail 58101 invoked by uid 500); 12 Jan 2004 14:13:18 -0000 Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@jakarta.apache.org Received: (qmail 58076 invoked by uid 500); 12 Jan 2004 14:13:18 -0000 Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Commons HttpClient Project" Reply-To: "Commons HttpClient Project" Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 58062 invoked from network); 12 Jan 2004 14:13:18 -0000 Received: from unknown (HELO mail.corp.idt.net) (207.202.32.33) by daedalus.apache.org with SMTP; 12 Jan 2004 14:13:18 -0000 Received: from [10.150.2.29] (HELO maxPCdrosen) by mail.corp.idt.net (CommuniGate Pro SMTP 4.0.6) with SMTP id 40251128 for commons-httpclient-dev@jakarta.apache.org; Mon, 12 Jan 2004 09:13:18 -0500 From: "David Rosenstark" To: "Commons HttpClient Project" Subject: RE: refresh header proxy Date: Mon, 12 Jan 2004 16:16:59 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: <825BF35A92B3F0479CC164ECBBE9376E0DE686@kccxoex06.corp.kpmgconsulting.com> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N ok, good point. I tried out just resending the requests twice and it did not work, so it obviously needs to be studied more and would probably require some additional headers be sent. By studying the logs, i found that the proxy server must be blue coat. One more thing. While it may not be standard - mozilla and IE handle this header just fine. I sent you the log (and not the list) as i was unsure whether the list rules would want something like that sent. Thanks, David -----Original Message----- From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com] Sent: Mon, January 12, 2004 3:25 PM To: Commons HttpClient Project Subject: RE: refresh header proxy > I think all you need to know is what the header looks like, as i did look at > the logs. It simply ignores the header. The header looks like this: > > Refresh: 0; URL=https://........ Well, things _may_ be a little bit more complicated than that. Therefore, the complete wirelog might be beneficial. Besides, the wirelog would also tell me what proxy server you are using. At the moment, having done some googling I failed to find any references to a 'refresh' header definition. If the header in question is a proprietary feature of the proxy server that you are using, I doubt it warrants the inclusion into the stock version of HttpClient. I believe the connection refresh stuff can be easily implemented with a little bit of code on top of standard HttpClient. Oleg -----Original Message----- From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com] Sent: Mon, January 12, 2004 2:51 PM To: Commons HttpClient Project Subject: RE: refresh header proxy David, No, it is not. However, as we are currently in the process of reengineering authentication/proxy code, if you provide the wirelog/debug of the HTTP session in question, we might be able to add such feature to the development branch of HttpClient in the forthcoming weeks For details on logging in HttpClient please refer to the HttpClient logging guide Cheers Oleg -----Original Message----- From: David Rosenstark [mailto:david.rosenstark@corp.idt.net] Sent: Monday, January 12, 2004 13:47 To: Commons HttpClient Project Subject: refresh header proxy Is the refresh header supposed to be supported by httpclient (latest version)? I have been trying to connect to a site (SSL) through our proxy and it send me back a header with refresh: 0, URL=https://..... and httpclient is not requesting it from there. TIA, David --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org