Re: refresh header proxy
David Rosenstark wrote: Is the refresh header supposed to be supported by httpclient (latest version)? There is not anything like a refresh header in HTTP. You probably mean the refresh feature of HTML. HTML is transported by HTTP as the message body. HttpClient does not try to interprete the message body and therefor does and will not support refresh. 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. Kind regards Ortwin Glück - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: refresh header proxy
I think these are teh relevant lines: 2004-01-12 15:21:14,406 [main] DEBUG httpclient.wire - Content-Type: text/html[\r][\n] 2004-01-12 15:21:14,406 [main] DEBUG httpclient.wire - Pragma: no-cache[\r][\n] 2004-01-12 15:21:14,406 [main] DEBUG httpclient.wire - Refresh: 0; URL=https://reports..com/users//file.csv[\r][\n]; 2004-01-12 15:21:14,406 [main] DEBUG httpclient.wire - Connection: Close[\r][\n] -Original Message- From: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED] Sent: Mon, January 12, 2004 2:58 PM To: Commons HttpClient Project Subject: RE: refresh header proxy There is not anything like a refresh header in HTTP. You probably mean Odi, that quite well may be, but to my best knowledge certain widely used proxy headers are not really defined by any RFCs. There are just common practices that most of the leading proxy servers adhere to (to an extent) like 'Proxy-connection' header. Refresh header may fall into such category of commonly used proxy headers. We should be able to tell if my theory is right by examining the wirelog of the session. Oleg - 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: refresh header proxy
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:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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 http://jakarta.apache.org/commons/httpclient/logging.html Cheers Oleg -Original Message- From: David Rosenstark [mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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] - 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: refresh header proxy
Kalnichevski, Oleg wrote: 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. [ ... ] I had to do some parsing of this type of header when writing a parser that extracted these from their in-html incarnation. At the time I couldn't find much out about them either. FWIW, the following regexp caught a lot of the html pages I saw in the wild: ;\s*[Uu][Rr][Ll]=\s*([^\s]+)\s*$ The main thing to watch out for was the variation in case of the URL= part. This may not be an issue if the header is generated by an actual http server (as opposed to being in some html or added by a CGI script). -- Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: refresh header proxy
All right. After having examined the wirelog you had sent me, I think I know what is going on. It looks like it has noting to do with that 'refresh' header. I believe you have been bitten by this bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20089 The bad news is that HttpClient 2.0 will never be able to handle SSL via proxy + host authentication due to severe design limitations. Your only chance is to use preemptive authentication. See the SSL guide for more details http://jakarta.apache.org/commons/httpclient/sslguide.html The good news is that the patch that should solve the problem for the development (read unstable) version has been (coincidentally) just approved: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25529 I'll commit the patch tonight. You may take to the next morning (that is, CET morning) nightly build for a spin and see if that makes any difference Cheers Oleg -Original Message- From: David Rosenstark [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 15:17 To: Commons HttpClient Project Subject: RE: refresh header proxy 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:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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 http://jakarta.apache.org/commons/httpclient/logging.html Cheers Oleg -Original Message- From: David Rosenstark [mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: refresh header proxy
ok, thanks. I will try to give it a try and let you know if it helps. -Original Message- From: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED] Sent: Mon, January 12, 2004 4:37 PM To: Commons HttpClient Project Subject: RE: refresh header proxy All right. After having examined the wirelog you had sent me, I think I know what is going on. It looks like it has noting to do with that 'refresh' header. I believe you have been bitten by this bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20089 The bad news is that HttpClient 2.0 will never be able to handle SSL via proxy + host authentication due to severe design limitations. Your only chance is to use preemptive authentication. See the SSL guide for more details http://jakarta.apache.org/commons/httpclient/sslguide.html The good news is that the patch that should solve the problem for the development (read unstable) version has been (coincidentally) just approved: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25529 I'll commit the patch tonight. You may take to the next morning (that is, CET morning) nightly build for a spin and see if that makes any difference Cheers Oleg -Original Message- From: David Rosenstark [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 15:17 To: Commons HttpClient Project Subject: RE: refresh header proxy 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:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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 http://jakarta.apache.org/commons/httpclient/logging.html Cheers Oleg -Original Message- From: David Rosenstark [mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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] - 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] - 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: refresh header proxy
Hello David, are you sure the browsers are handling the HTTP header field and not the contents of the HTML document returned? The syntax of the header field resembles the typical HTML refresh statement: meta http-equiv=refresh content=0; URL=... It is common (maybe even standard?) behaviour for browsers to interpret this meta tag, which does not mean they interpret the corresponding HTTP header. The header never became a standard, as pointed out by others. Have you tried to return a Refresh: header for a document that does definitely not contain the meta tag? cheers, Roland David Rosenstark [EMAIL PROTECTED] 12.01.2004 15:16 Please respond to Commons HttpClient Project To: Commons HttpClient Project [EMAIL PROTECTED] cc: Subject:RE: refresh header proxy 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:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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 http://jakarta.apache.org/commons/httpclient/logging.html Cheers Oleg -Original Message- From: David Rosenstark [mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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] - 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: refresh header proxy
I think I will assume that i misunderstood the problem based on Oleg's response. What i meant was that i knew that this proxy was not causing a problem to either of the browsers. What i found in my research was that this header is not a standard http 1.1 header but supported by netscape and IE -Original Message- From: Roland Weber [mailto:[EMAIL PROTECTED] Sent: Mon, January 12, 2004 5:18 PM To: Commons HttpClient Project Subject: RE: refresh header proxy Hello David, are you sure the browsers are handling the HTTP header field and not the contents of the HTML document returned? The syntax of the header field resembles the typical HTML refresh statement: meta http-equiv=refresh content=0; URL=... It is common (maybe even standard?) behaviour for browsers to interpret this meta tag, which does not mean they interpret the corresponding HTTP header. The header never became a standard, as pointed out by others. Have you tried to return a Refresh: header for a document that does definitely not contain the meta tag? cheers, Roland David Rosenstark [EMAIL PROTECTED] 12.01.2004 15:16 Please respond to Commons HttpClient Project To: Commons HttpClient Project [EMAIL PROTECTED] cc: Subject:RE: refresh header proxy 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:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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 http://jakarta.apache.org/commons/httpclient/logging.html Cheers Oleg -Original Message- From: David Rosenstark [mailto:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: refresh header proxy
Roland Weber wrote: meta http-equiv=refresh content=0; URL=... It is common (maybe even standard?) behaviour for browsers to interpret this meta tag, which does not mean they interpret the corresponding HTTP header. Roland, it may interest you that http-equiv meta parameters are actually meant to be treated as if they were sent as HTTP headers. So if the meta tag works in a browser, the HTTP header must work as well. Odi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: refresh header proxy
Not to beat a dead horse... but I was surprised this is a non-standard header so for anyone interested here are my of interest links. As Odi mentions Netscape introduced the header (the meta tag is the html equivalent to the (non-standard) http header.) Early draft refers to the Refresh header but marks it TBS http://www.w3.org/Protocols/HTTP/1.1/spec.html#Refresh Later an issue from the working group says the follow: was not in the 1.1 spec, due to unexplored security implications Post from a 2000 w3c list. Good information for anyone implementing the behavior expected and wanting to know why 3xx doesn't cover what's done in the Refresh: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0412.html The Netscape vision for the header. http://wp.netscape.com/assist/net_sites/pushpull.html JavaBoutique article showing usage. http://javaboutique.internet.com/tutorials/JSP/part08/page02.html mentions non-standard header, but that NS and IE support it. [trunc] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
