hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Rosenstark" <david.rosenst...@corp.idt.net>
Subject RE: refresh header proxy
Date Mon, 12 Jan 2004 14:56:30 GMT
ok, thanks. I will try to give it a try and let you know if it helps.

-----Original Message-----
From: Kalnichevski, Oleg [mailto:oleg.kalnichevski@bearingpoint.com]
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:david.rosenstark@corp.idt.net]
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: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 <http://jakarta.apache.org/commons/httpclient/logging.html>

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


---------------------------------------------------------------------
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


Mime
View raw message