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 b
Roland Weber wrote:
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
nd 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 ret
AIL 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
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
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
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 par
: 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
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 feat
Kalnichevski, Oleg wrote:
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 a
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,
" and request the page.
Do you need more info than this?
-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 t
> 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) li
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
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 l
15 matches
Mail list logo
