Fix multiple HTTP APIs incorrectly marked as supporting HTTPS - #1040
Open
JosephJonathanFernandes wants to merge 1 commit into
Open
Fix multiple HTTP APIs incorrectly marked as supporting HTTPS#1040JosephJonathanFernandes wants to merge 1 commit into
JosephJonathanFernandes wants to merge 1 commit into
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
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.
I noticed several APIs in the list explicitly used an http:// link (unencrypted) but were incorrectly marked as Yes in the HTTPS column.
I ran an audit script across the entire repository to find every API where the link strictly starts with http:// but the HTTPS column falsely claims Yes. I found exactly 25 APIs with this discrepancy.
This PR is a bulk fix that updates all 25 of these APIs to correctly display No in the HTTPS column, ensuring developers are not misled about the security of these endpoints