debugging config files options
Daniel Stenberg via curl-users <[email protected]>
| Newsgroups | gmane.comp.web.curl.general |
|---|---|
| Message-ID | <[email protected]> |
Hello, Sometimes users accidentally get "funny" or unexplainable behavior from curl command lines when they have options added in their .curlrc or other config files. The use of .curlrc is a little subtle and sometimes hard to spot and I have pondered on what we can do to make it easier to debug or trace what options are being used in such config files. A challenge is that ~/.curlrc is read and parsed before any command line options. So how do we active the config file debug mode? 1. If -v or --verbose is used as the *first option* on the command line. 2. If the environment variable named CURL_CONFIG_TRACE is set to 1. Or can we come up with a better way? -- / 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/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.html