Bugs item #2943699, was opened at 2010-02-01 06:14
Message generated for change (Comment added) made by christiansroy
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2943699&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: bad behaviour
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: aalbert (aalbert)
Assigned to: Daniel Stenberg (bagder)
Summary: Connection: Keep-Alive missing

Initial Comment:
According to the documentation, keep-alive is on by default, but can be set by --keepalive. In tests I performed, the Connection: header was missing and using --keepalive didn't help. I used WireShark to view the http. In fact the URL from which I was trying to download required Keep-Alive, so the download failed. Below is the User-Agent header (which shows the version). I'm running Vista SP2 32-bit.

User-Agent: curl/7.19.7 (i386-pc-win32) libcurl/7.19.7 zlib/1.2.3

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

Comment By: Christian Roy (christiansroy)
Date: 2010-02-01 16:34

Message:
aalbert

From what I understand of HTTP, the protocol 1.1 (default) does not need
to send the header for keep-alive since that is the default.

For HTTP/1.0, the keep-alive is not on by default. So using the
--keepalive is useful then.

Could that explain it?

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

Comment By: aalbert (aalbert)
Date: 2010-02-01 06:19

Message:
I should have included the command-line:

curl --keepalive --cookie "xxx=yyy"
http://user:pass@www.host.com/xxx/y.wmv

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

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2943699&group_id=976
Received on 2010-02-01