Closed jbhopkins closed 2 months ago
Hi,
I understand your concern, but I consider this bug is a consequence of the "https everwhere" option which has recently been enforced in most web-browsers. I am not a big fan of encrypting everything because it provides a false feeling of security and creates additional power consumption, but this is my personal point of view.
That said, we should probably enable https on edna-site (i.e. www.silx.org) to avoid those issues.
Concerning readthedocs, we use it as CI to ensure the doc still builds ... we don't use it for offering the documentation to the user, especially that there is no advertisement on edna-site.
@pierrepaleo as crypto-specialist, can you have a look at this. Should not be complicated.
Thanks for the comment, RTD is no more triggered by the CI ! This is actually a bug.
Updated the web server configuration to redirect http to https. Can you give it a try ?
Looks fixed ...
RTD is integrated back in CI
Thanks for taking a look at things so quickly! I'm still getting a warning about the certificate not being valid, though I can now get to the site.
I just tested with
It seems to work, at least for what the certificate itself is concerned. But I might have to test on more environments.
Perhaps your operating system is not configured to accept these letsencrypt certificates ?
If it helps, I see this in Safari and Chrome on MacOS (14.6.1) but not in Firefox.
The documentation here: http://www.silx.org/doc/fabio/latest/
Will not load in either chrome or firefox for me. Right now it either times out or I get an unsafe site message and can't override it to proceed. I'm assuming this has to do with it being http rather than https. Can you update to https? Or make sure the documentation on readthedocs (which is accessible and is https) is up to date with the latest version? Right now readthedocs seems to be at 2023.06 (https://fabio.readthedocs.io/en/main/Changelog.html)