| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| |
|
| |
The marker was only needed when we were testing Python 3.4.
|
| | |
|
| |
|
|
|
| |
It would have been better to generate them in tests/conftest.py, but
it's quicker to do it that way and since those new certs are compatible
with macOS 10.15 they will allow me to debug a SecureTransport issue.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* fix hang in TestSNI if client never connects
* handle insane ipv6 setup in tests
* update contributors
* more descriptive names in tests
Co-authored-by: Hod Bin Noon <bin.noon.hod@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Ensure load_verify_locations raises SSLError for all backends
This also adds TestSSL to the classes tested in SecureTransport and
PyOpenSSL, since:
1. TestSSL was the most natural place for this test.
2. The test only makes sense when run against all SSL backends.
Co-authored-by: Pierre-Louis Bonicoli <pierre-louis.bonicoli@libregerbil.fr>
* Remove redundant check in test
pytest.raises() already checks this.
* Update test_socketlevel.py
Co-authored-by: Pierre-Louis Bonicoli <pierre-louis.bonicoli@libregerbil.fr>
Co-authored-by: Seth Michael Larson <sethmichaellarson@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without `Content-Length: 0` or `Connection: close`, the client can try
reading more data after the socket gets closed. If it does try, it's
going to fail with "Connection reset by peer".
This was happening on Windows despite the `preload_content=False`
setting. Setting those headers fixes the issue and allows omitting
`preload_content=False`.
Since I'm a good citizen and want to close the sockets, I collect them
and close them when the connection pool is closed.
(I'm also renaming the test since it's specifically about the
Retry-After header.)
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This is just busywork, and never provided us any actual value. I've seen
yet another possible value in CI today: "Broken pipe".
https://travis-ci.com/github/pquentin/urllib3/jobs/297296688
We still check that there could be an error at the socket level or at
the SSL level, so the test is still helpful!
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add support to talk HTTPS to proxies.
Currently there's no way to validate identify for the proxy you might be
connecting. Proxies supporting HTTPS endpoints are becoming more common
and we need to extend the support for them.
When an HTTPS proxy is provided, instead of doing the HTTP CONNECT,
we'll forward any requests directly to the proxy and ultimately to the
destination.
* Fix proxy_headers missing on HTTPS proxy connections.
* blackfmt missing files.
* Prevent usage of HTTPS proxies when fetching HTTPS resources.
- Will be supported by default when we can do TLS within TLS.
* Update proxy documentation with more information.
* Renamed flag for HTTPS websites through HTTPS proxies.
* Added myself to contributors.
* Documentation and contributors fixes.
* Removed mention that TLS in TLS is being developed as requested.
* Space in between my name and the github page.
* Add flag to enable HTTPS proxy support.
Now that we're adding support for HTTPS proxies we want to avoid
a breaking change with clients that had an improper proxy configuration.
For now, we're adding a warning an defaulting to the previous behavior.
In the future we'll change the behavior to enable HTTPS proxies by
default.
* Remove guard flag, error out on HTTPS/HTTPS.
As requested in the last revision for the PR:
- Removed the _enable_https_proxies flag. Instead the feature will be
enabled and will error out on invalid configurations. (HTTPS + HTTPS)
- Other comments: rename a method, parentheses to clarify order of
operations.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Co-authored-by: Seth Michael Larson <sethmichaellarson@gmail.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
The next commit will generate the certificates using trustme.
|
| | |
|
| |
|
|
| |
Previously, iterating the lines of an empty response would yield the empty string once. However, the iterator should instead never yield anything. This is consistent with file io; `open('/dev/null', 'rb').readlines()` is `[]`.
|
| | |
|
| |
|
|
|
|
|
| |
Switching to pytest fixtures for those tests will allow to switch to
dynamically generated certificates in the future, without changing the
test. Using fixtures is easier than the existing setup because it's easy
to send information to the test about url, port and ca certs to use.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
It reached its end-of-life on 2019-03-18 and represents <4% of our
daily downloads.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Whether testbed tests "are appengine" is debatable, but historically
this function has returned False in testbed tests. This behavior was
inadvertently (and unnecessarily) changed in PR #1704. This commit
undoes that regression for testbed tests.
|
| | |
|
| | |
|
| |
|
|
| |
Unverified connections also go through VerifiedHTTPSConnection.
|