Bug-fix: Use SNI with media origin #78
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of issue
It was noticed recently that the Azure sample media streams we have been using on rt.5g-mag.com are now returning a 403 forbidden.
The streams were changed to similar streams from https://rdmedia.bbc.co.uk/ however this then generated a 502 error. This is due to an unknown SSL handshake failure.
Remedy
The servers being used by rdmedia.bbc.co.uk are general CDN servers, so it was postulated that the "rdmedia.bbc.co.uk" name was not being passed in the SNI allowing the CDN node to determine which server it is being a reverse proxy of. A quick test with OpenSSL tools confirmed this.
The solution is to add
proxy_ssl_server_name on;to the nginx http configuration to make it send an SNI when proxying requests.With the fix in place on the Linode instance we get a normal response from rdmedia.bbc.co.uk.