Well I guess I got my feedback :) Sorry I did not know it was on
purpose, I don't remember reading it on the mailing list.
So with enforced HTTPS off, we need to go a chase all the links in the
form of https://hibernate.org/foo and make them
https://hibernate.org/foo/ due to a limitation in GitHub
FWIW, I reverted it.
On Mon, Jul 30, 2018 at 6:33 PM Yoann Rodiere wrote:
> Also several users just reported that some wrong URL (
> http://hibernate.org/hibernate-configuration-3.0.dtd) used to work, and
> now doesn't. It started very recently.
>
> Did you change some HTTP redirection rules? Or
Also several users just reported that some wrong URL (
http://hibernate.org/hibernate-configuration-3.0.dtd) used to work, and now
doesn't. It started very recently.
Did you change some HTTP redirection rules? Or maybe we had a redirection
from http://hibernate.org/hibernate-configuration-3.0.dtd
Please be mindful of SEO as well. All existing valid URLs should
redirect to a valid HTTPS alternative before we switch.
On Mon, 30 Jul 2018 at 16:41, Guillaume Smet wrote:
>
> Please don't do it: there's a good reason I haven't done it: the news are
> not loaded because in.relation.to is not HTTP
Please don't do it: there's a good reason I haven't done it: the news are
not loaded because in.relation.to is not HTTPS.
We need to enable HTTPS for in.relation.to before doing it.
Thanks.
On Mon, Jul 30, 2018 at 4:43 PM Emmanuel Bernard
wrote:
> I've enforced HTTPS on hibernate.org.
> I am
I've enforced HTTPS on hibernate.org.
I am aware that Google Chrome shows warning as we load some non HTTPS
resources as part of the pages (two images, one link and the
in.relation.to feed).
But if you see other things not working, let us know.
Here is the issue tracker
https://hibernate.atlassian
