-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
The option «--dump-header» does not work correctly. #10074
Comments
I get 21 lines in all headers when using another shell. A Powershell issue? |
Repeat without manual deleting of dumps. Read more carefully: repeat some times. Repeat. Is the PowerShell clearing the file content? PowerShell does start external program and send options. Nothing more. Console of Cmd.exe:
10.12.2022 14:25 802 Header32.txt |
Using another arithmetics. An arithmetics issue? Empty line as end of dump you can not calculate? 1+20+1=22. The cURL does report, that num_headers=20. |
Yes this one is a bug. @emilengler |
See #4753 |
This commit fixes a bug, in which the tool appends to a text file instead of overwriting it, when a previous transfer took place. See curl#4753 See curl#4762 Fixes curl#10074 Closes #XXXX
This commit fixes a bug, in which the tool appends to a text file instead of overwriting it, when a previous transfer took place. See curl#4753 See curl#4762 Fixes curl#10074 Closes curl#10079
I looked at the regarding PRs and issues from 3 years ago. #4753 (comment) @jay: If I follow your logic correctly, I see a contradiction in these two comments. Could you elaborate? |
If you add, then to everyone. Why not add to the first? |
@emilengler there's a difference: This should put the headers from both transfers into the same file:
This should (probably) not append the headers to the files if they exist before the command line is invoked:
|
This commit fixes a bug in the dump-header feature regarding the determination of the second fopen(3) option. See curl#4753 See curl#4762 Fixes curl#10074 Closes curl#10079
This commit fixes a bug in the dump-header feature regarding the determination of the second fopen(3) option. See curl#4753 See curl#4762 Fixes curl#10074 Closes curl#10079
I did this
Start PowerShell 7.3.0 under the MS Windows and execute commands:
PS >
################################################################################ 100,0%
################################################################################ 100,0%
################################################################################ 100,0%
22
22
22
Repeat all above:
22
44
44
Repeat again:
22
66
66
And so on. All but the first header dump has incorrect content.
I expected the following
All header dumps contain an equal number of lines (22). Always.
curl/libcurl version
Build: 7.86.0_2
[curl -V output]
curl 7.86.0 (x86_64-w64-mingw32) libcurl/7.86.0 OpenSSL/3.0.7 (Schannel) zlib/1.2.13 brotli/1.0.9 zstd/1.5.2 WinIDN libssh2/1.10.0 nghttp2/1.51.0 ngtcp2/0.11.0 nghttp3/0.7.1 libgsasl/2.2.0
Release-Date: 2022-10-26
Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp ws wss
Features: alt-svc AsynchDNS brotli gsasl HSTS HTTP2 HTTP3 HTTPS-proxy IDN IPv6 Kerberos Largefile libz MultiSSL NTLM SPNEGO SSL SSPI threadsafe TLS-SRP UnixSockets zstd
operating system
MS Windows 10 last version with all updates
The text was updated successfully, but these errors were encountered: