Hello Charles,
you suspect correctly, the login form comes from
https://reg.racingpost.co.uk/cde/login_iframe.sd
as you can easily verify by accessing that URL directly
in your browser. From there, the login form is sent as
a POST request to reg.racingpost.co.uk
HttpClient can deal with the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Thanks Roland - that's a great start!
CJ
- Original Message -
From: Roland Weber [EMAIL PROTECTED]
To: Commons HttpClient Project [EMAIL PROTECTED]
Sent: Monday, January 12, 2004 9:16 AM
Subject: Re: Horseplay - https
Hello Charles,
you suspect correctly, the login form comes from
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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;
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
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
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
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
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26060.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
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
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
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
Thank you Oleg Mark for your help!!!
I'll write a workaround FilePart that do not convert the filename to
us-ascii!!!
Oleg:
if you fix the problem, can you send an email to me or to the mailing
list please! Thanks!
Steph
Oleg Kalnichevski wrote:
Is it a requirement that Disposition
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25529.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10794.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20089.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26070.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25592.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
You should send this to the HttpClient dev list.
subscribe: [EMAIL PROTECTED]
post: [EMAIL PROTECTED]
It looks as though the name used for the file is currently converted to
ascii bytes when the disposition header is written:
in o.a.c.h.methods.multipart.FilePart:
/**
* Write the
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
26 matches
Mail list logo
