Skip to content

Add SNI support for API HTTPS endpoint #4423

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 2, 2018
Merged

Conversation

agjohnson
Copy link
Contributor

This allows us to use a production internal loadbalancer without forcing
readthedocs.org resolves to the internal loadbalancer.

This allows us to use a production internal loadbalancer without forcing
`readthedocs.org` resolves to the internal loadbalancer.
@agjohnson agjohnson requested a review from a team July 24, 2018 19:42
@agjohnson agjohnson added the Improvement Minor improvement to code label Jul 24, 2018
@agjohnson agjohnson added this to the Azure migration milestone Jul 24, 2018
Copy link
Contributor

@davidfischer davidfischer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems fine. Here's the relevant docs from requests-toolbelt.

@agjohnson
Copy link
Contributor Author

Updated this, it worked for api v1, but needed some more changes for api v2.

@agjohnson agjohnson merged commit 6f02839 into master Aug 2, 2018
@agjohnson agjohnson deleted the agj/add-api-client-ssl-sni branch August 2, 2018 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Minor improvement to code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants