Bugs item #2956968, was opened at 2010-02-22 19:01
Message generated for change (Comment added) made by sidneysm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2956968&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: https
Group: wrong behaviour
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sidney San Martín (sidneysm)
Assigned to: Daniel Stenberg (bagder)
Summary: Can't PUT file from stdin with https and digest auth

Initial Comment:
I'm unable to PUT a file from stdin (-T -) when using an HTTPS server and digest authentication. If I change any of the three variables (specify a filename on -T, don't use digest auth, or use plain HTTP), the PUT succeeds. Attached is a trace. The command line used to generate it was:

curl --digest -k -u user:pass --trace trace_iphone -T - https://172.20.1.32/file3.txt < file

cURL version 7.20.0.

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

>Comment By: Sidney San Martín (sidneysm)
Date: 2010-06-14 22:10

Message:
You can reproduce the issue manually, right? If not, I'd be happy to help
narrow it down.

If so, I'll stop poking you :) .

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

Comment By: Daniel Stenberg (bagder)
Date: 2010-04-10 08:08

Message:
Thanks. I've had trouble repeating this problem with our test suite, as it
is kind of limited in functionality to run this scenario, but I'll continue
and see if I can't push it into compliance so that I can debug this in this
controlled environment.

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

Comment By: Sidney San Martín (sidneysm)
Date: 2010-04-06 19:43

Message:
--anyauth results in different behavior. Where --digest just hangs after
the first Continue (never tries to send any data), --anyauth outputs "curl:
(65) seek callback returned error 2" and exits. --trace shows that it
successfully sends the data once and throws the error after receiving the
401 response and headers.

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

Comment By: Daniel Stenberg (bagder)
Date: 2010-04-06 17:15

Message:
Thanks for reporting this issue and helping us improve curl and libcurl.

We're awaiting feedback in this issue. Due to this, I have set the state
of this issue to pending and it will automatically get closed later on
unless we get further info.

Please consider answering the outstanding questions or providing the
missing info so that we can proceed to resolve this issue!

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

Comment By: Daniel Stenberg (bagder)
Date: 2010-04-04 16:58

Message:
What happens if you use --anyauth instead of Digest?

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

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