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
The failure to use HTTPS puts visitors to the website at increased risk of various attacks. This might be less of a concern if pearsearch.org did not expect visitors to execute JavaScript, but it does.
Resolving #5 would potentially also resolve this issue, by migrating pearsearch.org (and indeed the rest of the PeARS project's code hosting) off GitHub and onto a host that does support HTTPS for custom domains.
Thanks!
The text was updated successfully, but these errors were encountered:
As an interim solution (i.e. not requiring the investment of time, attention and money required by self-hosting), you could still potentially solve this by resolving #5 :)
Sorry we're being slow with this -- most of PeARS team is currently either travelling or battling with urgent neural networks unrelated to PeARS ;) But yes, we have #5 on our discussion list for the next meeting. Thanks!
pearsearch.org is not currently served over HTTPS.
This is due to GitHub bug #156: Add HTTPS support to Github Pages including custom domains.
The failure to use HTTPS puts visitors to the website at increased risk of various attacks. This might be less of a concern if pearsearch.org did not expect visitors to execute JavaScript, but it does.
Resolving #5 would potentially also resolve this issue, by migrating pearsearch.org (and indeed the rest of the PeARS project's code hosting) off GitHub and onto a host that does support HTTPS for custom domains.
Thanks!
The text was updated successfully, but these errors were encountered: