Skip to content
This repository was archived by the owner on Jul 21, 2025. It is now read-only.

Conversation

raklaptudirm
Copy link

Previously the https-everywhere link redirected to https://https-everywhere.badssl.com/, which would always show the https page, thus not checking for the protocol update. This has been changed to redirect to http://https-everywhere.badssl.com/, so that a protocol upgrade can actually be observed.

…date occurs

Previously the `https-everywhere` link redirected to `https://https-everywhere.badssl.com/`, which would always show the https page, thus not checking for the protocol update.
This has been changed to redirect to `http://https-everywhere.badssl.com/`, so that a protocol upgrade can actually be observed.
Copy link

google-cla bot commented Aug 22, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@lgarron
Copy link
Contributor

lgarron commented Aug 31, 2024

This seems fairly reasonable to me, but the title of this PR doesn't make sense to me. This isn't changing any redirection, it's just updating the link on the index page, right?

@raklaptudirm
Copy link
Author

@lgarron Yes, that is what I meant. Feel free to change the name of the pr to something clearer.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants