libs3 currently does not write any logs, making it difficult to troubleshoot errors. This is particularly problematic in the case of libcurl errors, since a lot of libcurl's error codes are translated to S3StatusInternalError without any further info.
It would be very useful if libs3 allowed enabling detailed logs for the progress of requests, e.g., via an S3_set_log_level() function and S3_LOG_LEVEL environment variable. Also, it would be useful to allow enabling libcurl verbose mode (CURLOPT_VERBOSE) without having to rebuild libs3.
libs3currently does not write any logs, making it difficult to troubleshoot errors. This is particularly problematic in the case oflibcurlerrors, since a lot oflibcurl's error codes are translated toS3StatusInternalErrorwithout any further info.It would be very useful if
libs3allowed enabling detailed logs for the progress of requests, e.g., via anS3_set_log_level()function andS3_LOG_LEVELenvironment variable. Also, it would be useful to allow enablinglibcurlverbose mode (CURLOPT_VERBOSE) without having to rebuildlibs3.