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
Many of our PURLs redirect to HTTP resources that are also served via HTTPS. (Often those HTTP resources already redirect to their HTTPS versions.) It would be better for these to redirect to HTTPS instead. This is purely a matter of updating our configurations in this repository.
We should write scripts to:
collect the HTTP targets
group them by domain and sort by frequency
migrate known-good cases to HTTPS
report on the leftovers for manual review
Any volunteers?
The text was updated successfully, but these errors were encountered:
Extending 2 and 3: We could collect a list of distinct HTTP target URLs, and then request them to see if they redirect (HTTP 30x) to HTTPS URLs. Those would be good candidates for replacement, although I would want a human to check the results.
Many of our PURLs redirect to HTTP resources that are also served via HTTPS. (Often those HTTP resources already redirect to their HTTPS versions.) It would be better for these to redirect to HTTPS instead. This is purely a matter of updating our configurations in this repository.
We should write scripts to:
Any volunteers?
The text was updated successfully, but these errors were encountered: