Eric Johnson wrote:
Redirect on a POST request
is *not supported*
This stems from fundamental architectural limitations of the current
HttpClient 2.0 design.
Actually the problem is two-fold:
1. redirect in HttpClient means: The *same* request ist sent to a
different URL (on the same
Catalin Ionescu wrote:
Jan. 09-2003
I use a httpclient to download a file on a daily basis from https website
The site has:
VeriSign International Server CA - Class 3
It was working all 2003 and I have installed httpclient version as Feb. 25th 2003 that was available, but yesterday suddenly
Folks,
What say you, do we migrate HttpClient issue tracking to JIRA or do we
stay with Bugzilla? Please let me know your opinion.
Oleg
On Tue, 2004-01-13 at 20:29, Oleg Kalnichevski wrote:
Shall I apply? Any strong opinions to not migrate to JIRA?
Oleg
On Tue, 2004-01-13 at 20:01,
Oleg Kalnichevski wrote:
Folks,
What say you, do we migrate HttpClient issue tracking to JIRA or do we
stay with Bugzilla? Please let me know your opinion.
Oleg
Sorry, I have not had the time to take a look at JIRA and I don't know
that product at all. All I can say is that I am quite familiar
Thanks for your explanation. So I am okay with moving to JIRA. Now is
really a good time, since the number of open bugs is relatively small.
What about existing (old) bugs? Can those be migrated somehow automatically?
Odi
Kalnichevski, Oleg wrote:
Odi,
One nastiest thing about Bugzilla is its
Is there an automatic way to move the current issues over to JIRA? The open
bugs are important, but the closed ones also contain a wealth of
information.
Thanks
Moh
-Original Message-
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 6:41 AM
To: Jakarta
Is there an automatic way to move the current issues over to JIRA? The open
bugs are important, but the closed ones also contain a wealth of
information.
I do not have all the details, but JIRA is believed to provide some sort of an
automated migration path for existing Bugzilla
Dave,
You should not blindly relay a server's response directly to the client
if you are not bahaving like a good HTTP proxy (not even a proxy does it
blindly actually, it processes the headers). You should rather parse and
interprete the server's response and craft a response suitable for
You should not blindly relay a server's
response directly to the client
if you are not bahaving like a good HTTP proxy
(not even a proxy does it
blindly actually, it processes the headers).
Ok, sorry in advance, I'm sort of a novice at all
of this, but why not? Also, let's just
theoretically
D Alvarado wrote:
Ok, sorry in advance, I'm sort of a novice at all
of this, but why not? Also, let's just
theoretically say that someone else (not me, of
course), just blindly spit back the response. Is
it possible to tell the client to treat the
response in the context of www.otherdomain.com
Well, I'm not sure how I would recommend going on this decision. So
here is my attempt at providing a slightly biased (in favor of Bugzilla)
view of the facts.
I looked at nagoya.apache.org, and checked out both the Scarab and Jelly
installations running there.
Random observations:
*
My suggestion would be to also investigate the possibility of HttpClient
being promoted (in Bugzilla only) to a project rather than a component
of commons, and also see about having the Bugzilla version updated.
Eric,
I think it's a brilliant idea. It does make sense that HttpClient gets
If you try and think this through carefully,
you will see that the term
in the context of will inadvertly lead to
ambiguities. What about
images referenced by the document, how must they
be resolved? What about
links to other domains, do we still have to use
the proxy or can we
just reach
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=24012.
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=24012.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
D Alvarado wrote:
Ok, well I definitely won't pursue the blind
route. How would an HTTP Proxy behave in this
situation? Surely it wouldn't parse out HTML.
The thing is, the proxy doesn't have to. The client understands the
proxy protocol. It *explicitly* requests the page *through the proxy*,
does httpclient have an API for creating a
Authentication Digest? if so what all does it need for
that apart from the realm, username and the password?
__
Do you Yahoo!?
Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes
I just discovered a bug introduced with the recent changes in the authentication logic
for which I bear full responsibility. Basically NTLM authentication scheme fails to
properly handle authentication failures caused by invalid credentials, and a result
HttpClient enters an infinite loop in
I agree these are some good idea Eric. The one main problem, as it has
been discussed on commons-dev, is that no-one seems to be interested in
maintaining Bugzilla. This is why we are using such an old version.
This seems to be a key issue for some of the other commons projects.
Mike
On
Hi Sid,
Take a look at the DigestScheme
http://jakarta.apache.org/commons/httpclient/apidocs/org/apache/
commons/httpclient/auth/DigestScheme.html.
Mike
On Jan 21, 2004, at 1:37 PM, Sid Subr wrote:
does httpclient have an API for creating a
Authentication Digest? if so what all does it need
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=26139.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
would it be possibe to the following
send a request to web server . get authentication
response. read the response use the nonce and create
the digest with the nonce and then send out the
request again with the authorization digest
--- Michael Becke [EMAIL PROTECTED] wrote:
Hi Sid,
Take a
Hi Sid,
Yes, HttpClient already handles Digest authentication for you. Please
take a look at the authentication docs
http://jakarta.apache.org/commons/httpclient/authentication.html.
You just need to provide credentials.
Mike
On Jan 21, 2004, at 4:31 PM, Sid Subr wrote:
would it be
23 matches
Mail list logo
