Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Printing the URL in the error messages when --fail is passed?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>
Date: Sun, 24 Jul 2022 23:57:48 +0200 (CEST)
On Sun, 24 Jul 2022, Bhavin Gandhi via curl-users wrote:
> I'm new to curl code, but based on what we decide, I can help in doing this
> change.
The reason those details are not present in the error messages already, is
that it isn't that clear-cut as to how and when to include what in the error
messages.
I'm all for improving them, but it might require some proper thinking and
planning first.
Some questions to ponder:
1. Should the URL be included in all error messages? If not all, which ones?
2. If you use the same URL in multiple places in the cmdline, then how does
the error message differentiate between *which* of the identical URLs it is in
regards to?
3. If there's a file associated with the URL (for example, we upload file A
to URL B), should that file name be included too in error messages? How? In
which error messages?
4. Most error messages come "provided" by the library and the client code only
passes them through. How should the process be to add the URL/file name into
the error message to show?
Date: Sun, 24 Jul 2022 23:57:48 +0200 (CEST)
On Sun, 24 Jul 2022, Bhavin Gandhi via curl-users wrote:
> I'm new to curl code, but based on what we decide, I can help in doing this
> change.
The reason those details are not present in the error messages already, is
that it isn't that clear-cut as to how and when to include what in the error
messages.
I'm all for improving them, but it might require some proper thinking and
planning first.
Some questions to ponder:
1. Should the URL be included in all error messages? If not all, which ones?
2. If you use the same URL in multiple places in the cmdline, then how does
the error message differentiate between *which* of the identical URLs it is in
regards to?
3. If there's a file associated with the URL (for example, we upload file A
to URL B), should that file name be included too in error messages? How? In
which error messages?
4. Most error messages come "provided" by the library and the client code only
passes them through. How should the process be to add the URL/file name into
the error message to show?
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2022-07-24