Bugs item #1969808, was opened at 2008-05-22 14:51
Message generated for change (Comment added) made by iturrajoel
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1969808&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: http
Group: wrong behaviour
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Joel Iturra (iturrajoel)
Assigned to: Daniel Stenberg (bagder)
Summary: libcurl dont recognize connection close

Initial Comment:
Hi,
I am using curl 7.18.1 and I have one problem. I think it is confluence of situations

*) HTTP Server: Weblogic Server 8.1 SP2
*) connection is too bad (very remote location)
*) libcurl dont see the connection is closed

Debug lines:

< HTTP/1.1 302 Moved Temporarily
< Date: Thu, 22 May 2008 18:14:52 GMT
< Location: http://URL/psp/finzp/EMPLOYEE/ERP/h/?tab=DEFAULT
< Server: WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
< Content-Type: text/html
< Expires: Thu, 01 Dec 1994 16:00:00 GMT
< Transfer-Encoding: chunked
< Connection: Close
* Issue another request to this URL: 'http://URL/psp/finzp/EMPLOYEE/ERP/h/?tab=DEFAULT'
* Examining connection #0 for reuse
* Re-using existing connection! (#0) with host URL
* Connected to URL (IP) port 80 (#0)
> GET /psp/finzp/EMPLOYEE/ERP/h/?tab=DEFAULT HTTP/1.1

As you can see, the server close the connection, but libcurl dont detect and try to use the same #0.
Result, no data received.

(please forgive my english)

Thank you
Joel

----------------------------------------------------------------------

>Comment By: Joel Iturra (iturrajoel)
Date: 2008-05-22 15:49

Message:
Logged In: YES
user_id=2095540
Originator: YES

Linux: Mandriva Linux release 2007.1 (Official) for i586
Kernel: 2.6.17-13mdv #1 SMP

(C program, relevant lines)

curl_easy_setopt(curl_handle,CURLOPT_FOLLOWLOCATION,config_obj->redir_auto);
 // true
curl_easy_setopt(curl_handle,CURLOPT_FRESH_CONNECT,1);
curl_easy_setopt(curl_handle,CURLOPT_FORBID_REUSE,1);
curl_easy_setopt(curl_handle,CURLOPT_DNS_CACHE_TIMEOUT,-1);
curl_easy_setopt(curl_handle,CURLOPT_ENCODING,"identity");
curl_easy_setopt(curl_handle,CURLOPT_AUTOREFERER,1);
curl_easy_setopt(curl_handle,CURLOPT_NOPROGRESS,1);
curl_easy_setopt(curl_handle,CURLOPT_VERBOSE,1);
curl_easy_setopt(curl_handle,CURLOPT_COOKIEJAR,cookiejarfile->str);
curl_easy_setopt(curl_handle,CURLOPT_COOKIESESSION,1);
curl_easy_setopt(curl_handle,CURLOPT_NOSIGNAL,1);

Note:
this behavior not always happens and while better connection, better
behavior of the client

How I can test when the connection is broken ?

----------------------------------------------------------------------

Comment By: Dan Fandrich (dfandrich)
Date: 2008-05-22 15:17

Message:
Logged In: YES
user_id=236775
Originator: NO

This looks a lot like test case 11 in the test suite, which passes fine. I
tried modifying it to more closely match exactly these headers and it still
works fine. What command-line options are you using? What platform is this
on?

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1969808&group_id=976
Received on 2008-05-22