Juan,
please take a look at our logging guide:
http://jakarta.apache.org/commons/httpclient/logging.html
Try and get a wirelog of the communication. That will help to track down
the problem.
Cheers
Ortwin Glück
Juan Pedro López Sáez wrote:
Hello all.
From time to time I'm getting the following
Juan,
Most likely it is a server side issue. Take a look at this post. It
should explain the cause of the problem and can help find a fix for it
http://marc.theaimsgroup.com/?l=httpclient-commons-devm=109344163805313w=2
Oleg
On Thu, 2004-09-09 at 10:24, Juan Pedro Lpez Sez wrote:
Hello all.
Hello,
In case it is a server side issue, I would like be sure that the server
hasn't processed my request because I'm posting non idempotent requests.
If I retry the request but the first one was really processed I could be
in troubles.
I guess there is not a simple solution for this.
I
Juan,
There's indeed no easy solution to this problem. There's a whole section
in our new exception handling guide on the issue of the transport safety
and HTTP methods' idempotency. The guide has not been published yet, as
it describes the new exception handling framework in the upcoming
Juan,
The one technique that I'm aware of for guaranteeing that the server
only processes the request once is to put in some sort of transaction ID
into the request, and the server will reject duplicate requests
(hopefully with an appropriate error message).
In short, it is an application
Hello.
I return with my problem, now with more information.
Guys at the server side (the use Apache) told me they don't have any
problem related to dropping connections, and even they assure me the
server did receive my request and at least logged the response.
They have two servers: the main
Juan Pedro López Sáez wrote:
If the
request doesn't success, PostMethod.releaseConnection() isn't called
You must *always* call releaseConnection, whether the request was
successful or not. Do it in a finally block. Missing a call to
releaseConnection will lead to resource leaks.
--
: Juan Pedro López Sáez [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 10, 2004 16:28
To: Commons HttpClient Project
Subject: Re: unable to find line starting with HTTP
Hello.
I return with my problem, now with more information.
Guys at the server side (the use Apache) told me they don't have
Thank you for your responses.
Actually, I can't do anything in the server side because it's managed by
an external service provider. I don't know what server are they running
but I'll try to find it.
I thought the problem was in the client side, but now I think I'll try
to ask them to solve the
Juan,
Usually HttpClient reports 'unable to find line starting with HTTP' when the target
server drops the connection without returning any response. This can happen, for
instance, if the server is being under heavy load.
(1) If you have access to the target server, examine the server logs to
I am seeing this exact same problem with 2.0rc1 as well. A wget to the
server from the same client works fine. The httpclient wire log shows
that I get a redirect and then the in waiting for the HTTP status line
from the redirect, it never comes...
What server are you running?
-Eric
Dr. K.M. Ku wrote:
Roottelnet www.worldscinet.com 80
Trying 203.208.144.142...
Connected to www.worldscinet.com.
Escape character is '^]'.
GET /ijac/14/1401/S02181967041401.html HTTP/1.0
html
body bgcolor=#FF
div align=center
[...]
I cannot find the response header. I think this is the
Hello KMKU,
It looks like this second URL
http://www.worldscinet.com/ijac/14/1401/S02181967041401.html is not
being server by an HTTP server. As you note it just writes a bunch of
content without any headers. There's not much we can do about this
one, as HttpClient only supports working
OK. Now I know what is going on here. The server simply send the HTML
page body without ANY response header of what so ever. No wonder
HttpClient cannot find a status line. Stuff like that cannot work, as
far as I am concerned. Feel free to drop the webmaster of that site a
line.
Oleg
Hi Michael,
Well I'll be darned. I'd actually half written an email telling you to
try the latest HttpClient because the problem was fixed when I actually
tried the latest HttpClient and watched it barf. So yeah, that one's a
bug that will need to be fixed, the headers looked pretty
15 matches
Mail list logo
