Minecraft CDN moved over to HTTPS #45
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
jimnordb
changed the title
|
Damn... Thanks for the PR.. |
|
that should solve it! |
|
Thanks, good PR |
Closed
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.
What CDN does this PR relate to
download.minecraft.net
Does this require running via sniproxy
Yes
Capture method
Fiddler 4
Testing Scenario
Tested at home, setup a SNIproxy, 4 different lancaches (Uplay, Steam, Blizzard and Minecraft) using steamcache/generic. Steamcache, Blizzard and Uplay works smoothly after setting DNS ip to server ip hosting steamcache-dns. Minecraft uses https now instead.
Sniproxy output
2018-12-09 16:17:21 192.168.1.43:34138 -> 0.0.0.0:443 -> 143.204.47.64:443 [resources.download.minecraft.net] 47819730/47819730 bytes tx 296544/296544 bytes rx 10.343 seconds