Parallel request failures don't include url in error message #6199
Labels
Comments
... and even with a URL shown it could be hard to tell if you for example use the same URL multiple times and only one or some of them fail! Maybe it should then also refer to which number of the URL it was? |
I hadn't thought of that scenario as my use cases have always used unique urls. Perhaps the idea of indexing them can work as curl already has the notion of position dependent urls and options on the command-line. |
bagder
added a commit
that referenced
this issue
Nov 15, 2020
Primarily to help the user understand which error message goes with which URL when multiple URLs have been provided. Reported-by: Earnestly on github Fixes #6199
bagder
added a commit
that referenced
this issue
Nov 20, 2020
In particular, these ones can help a user to create its own error message when one or transfers fail. writeout: add 'onerror', 'url', 'urlnum', 'exitcode', 'errormsg' onerror - lets a user only show the rest on non-zero exit codes url - the input URL used for this transfer urlnum - the numerical URL counter (0 indexed) for this transfer exitcode - the numerical exit code for the transfer errormsg - obvious Reported-by: Earnestly on github Fixes #6199
bagder
added a commit
that referenced
this issue
Nov 28, 2020
In particular, these ones can help a user to create its own error message when one or transfers fail. writeout: add 'onerror', 'url', 'urlnum', 'exitcode', 'errormsg' onerror - lets a user only show the rest on non-zero exit codes url - the input URL used for this transfer urlnum - the numerical URL counter (0 indexed) for this transfer exitcode - the numerical exit code for the transfer errormsg - obvious Reported-by: Earnestly on github Fixes #6199 Closes #6207
bagder
added a commit
that referenced
this issue
Dec 14, 2020
In particular, these ones can help a user to create its own error message when one or transfers fail. writeout: add 'onerror', 'url', 'urlnum', 'exitcode', 'errormsg' onerror - lets a user only show the rest on non-zero exit codes url - the input URL used for this transfer urlnum - the numerical URL counter (0 indexed) for this transfer exitcode - the numerical exit code for the transfer errormsg - obvious Reported-by: Earnestly on github Fixes #6199 Closes #6207
bagder
added a commit
that referenced
this issue
Dec 20, 2020
In particular, these ones can help a user to create its own error message when one or transfers fail. writeout: add 'onerror', 'url', 'urlnum', 'exitcode', 'errormsg' onerror - lets a user only show the rest on non-zero exit codes url - the input URL used for this transfer urlnum - the numerical URL counter (0 indexed) for this transfer exitcode - the numerical exit code for the transfer errormsg - obvious Reported-by: Earnestly on github Fixes #6199 Closes #6207
bagder
added a commit
that referenced
this issue
Dec 21, 2020
In particular, these ones can help a user to create its own error message when one or transfers fail. writeout: add 'onerror', 'url', 'urlnum', 'exitcode', 'errormsg' onerror - lets a user only show the rest on non-zero exit codes url - the input URL used for this transfer urlnum - the numerical URL counter (0 indexed) for this transfer exitcode - the numerical exit code for the transfer errormsg - obvious Reported-by: Earnestly on github Fixes #6199 Closes #6207
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When making use of the new parallel feature it it appears that any request failures don't include the url from which the error came from. For example I have seen the following:
Due to the lack of a url in the message itself, it's hard to know where these errors are from to take any corrective action.
curl
versionThe text was updated successfully, but these errors were encountered: