You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
We don't use S3 anymore and haven't used it for a very long time. This particular change broke our product since users with HTTPS anywhere installed received old and invalid code from S3. We had to workaround this by uploading our code to S3 which cannot be a permanent solution.
Activity
jsha commentedon Aug 28, 2015
Thanks for the report @j-manu, and sorry for breaking your product. Would you like us to disable the whole rule, or just remove the S3 part?
j-manu commentedon Aug 29, 2015
Disable the whole rule.
We don't and can't have HTTPS enabled for the CDN domain as we need to support legacy clients and though we do support HTTPS, the target might change
HTTPS for our main domain will not work 100% since we embed third party content which may not be HTTPS
So right now, auto redirecting of HTTP traffic to HTTPS like what https-everywhere does is not an option for us.
J0WI commentedon Sep 5, 2015
Could you provide a pull request adding
default_off="webmaster request"?j-manu commentedon Sep 8, 2015
@J0WI Done. #2821
jsha commentedon Sep 28, 2015
Fixed, thanks for submitting that pull request @j-manu.