Improved handling of self-signed certs when uploading with known URL #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When following the example in the README to upload data to a known files path, an exception will be raised if the server uses a self-signed certificate. Passing the option
verify_tls_cert=False
as input to the Uploader constructor does not apply this setting to all the functions involved, thus triggering an exception.Solution
The culprit for this exception is two-fold. First is the positioning of
self.verify_tls_cert = verify_tls_cert
. In the current position this configuration will not be reached before an exception is raised; moving this line to the top resolves this.The second issue is in the HEAD request made by the
baseuploader.py
script. The made HEAD request lacks the addition of theverify_tls_cert
option defined in the Constructor. Adding this configuration to the HEAD request resolves this and makes it function similar to PATCH requests made in similar fashion.Tests
I have tried running the present tests via
python setup.py test
and all the tests have passed for this change.Expand for tests