Use HTTPS for OptiFine capes #132
Merged
Conversation
This file contains hidden or 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
Member
Author
|
This is untested because I failed to compile the twoconfig branch successfully |
|
There is another class you are missing, net.optifine.http.HttpUtils, which does all non cape cosmetics (like christmas hats and whatnot). the method is getPlayerItemsUrl |
Member
Author
|
still untested, polypatcher does NOT compile (for me at least idk) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
Makes OptiFine use HTTPS connection for capes
Related Issue(s)
Was on Discord, Wyvest told me to PR it
How to test
Release Notes
Documentation