You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is true and has been so virtually forever. I'm not sure I think this is something we should change.
The upside is that you know for sure when no headers have been delivered by curl, especially if you re-run the command line as then it could otherwise have the previous file contents lying around.
The make-no-file-if-nothing-to-write concept was abandoned for cookies for pretty much this reason, which makes me now lean towards favoring empty-files-for-empty-responses. Like this. Especially since this behavior has been here for a long time so scripts and users have gotten used to and come to rely on this by now.
This is true and has been so virtually forever. I'm not sure I think this is something we should change.
The upside is that you know for sure when no headers have been delivered by curl, especially if you re-run the command line as then it could otherwise have the previous file contents lying around.
The make-no-file-if-nothing-to-write concept was abandoned for cookies for pretty much this reason, which makes me now lean towards favoring empty-files-for-empty-responses. Like this. Especially since this behavior has been here for a long time so scripts and users have gotten used to and come to rely on this by now.
Fair.
My only issue is that when running on multiple sites it creates a discrepancy between the number of files created to number of active sites.
I did this
Created file test_header.txt
I expected the following
dump-header file is not created until valid response headers are received.
curl/libcurl version
operating system
macOS 10.14
The text was updated successfully, but these errors were encountered: