Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using proxy with negotiate, POST with content length zero ends with too many redirects #4996

Closed
IvanoG opened this issue Feb 28, 2020 · 5 comments
Closed

Using proxy with negotiate, POST with content length zero ends with too many redirects #4996

IvanoG opened this issue Feb 28, 2020 · 5 comments
Labels
HTTP

Comments

@IvanoG
Copy link

IvanoG commented Feb 28, 2020

Operating system: Windows 2016
curl version: 7.68

curl.exe -X POST -x user:password@proxy --proxy-negotiate server_address -d ""

I expected to receive an answer from the server_address.

The result is "too many redirects". It works with -d "something"
@bagder
Copy link
Member

bagder commented Feb 28, 2020

You need to show us details from the HTTP protocol exchange! Without that we can't do anything. (and you don't want/need -X POST in that command line)

Perhaps add --trace-ascii log.txt to the command line and attach that file here? (after you'd made sure it doesn't contain anything sensitive)

@IvanoG
Copy link
Author

IvanoG commented Feb 29, 2020

I attached the requested file log.txt

@bagder bagder removed the needs-info label Feb 29, 2020
@bagder
Copy link
Member

bagder commented Feb 29, 2020

I have an idea. I'll propose a PR in a sec...

bagder added a commit that referenced this issue Feb 29, 2020
@bagder
http: mark POSTs with no body as "upload done" from the start
b0458a5 
As we have logic that checks if we get a >= 400 reponse code back before
the upload is done, which then got confused since it wasn't "done" but
yet there was no data to send!

Reported-by: IvanoG
Fixes #4996
@bagder bagder mentioned this issue Feb 29, 2020
Closed
@bagder
Copy link
Member

bagder commented Mar 1, 2020

@IvanoG, it would be great if you could confirm that this patch actually fixes your problem!

bagder added a commit that referenced this issue Mar 2, 2020
@bagder
http: mark POSTs with no body as "upload done" from the start
1460c1b 
As we have logic that checks if we get a >= 400 reponse code back before
the upload is done, which then got confused since it wasn't "done" but
yet there was no data to send!

Reported-by: IvanoG on github
Fixes #4996
Closes #5002
@bagder bagder closed this as completed in 0caae3c Mar 2, 2020
@IvanoG
Copy link
Author

IvanoG commented Mar 3, 2020

The fix solved the problem. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
HTTP
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

http: mark POSTs with no body as "upload done" from the start curl/curl
2 participants
@bagder @IvanoG