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]
