Migrating codimd to hedgedoc with apache reverse proxy about container HOT 3 CLOSED

Instead of "Now you can follow the regular update steps.", we could add a link to the release notes. This would at least prompt folks to read them. I'll make a PR updating the README.

from container.

Apache by default does not set the X-Forwarded-Proto header, which leads to HedgeDoc not setting login cookies when protocolUseSSL is enabled (we discovered that in this issue).
Have a look at the docs for a working Apache config.

We also added a note about that header in the changelog of 1.7.0, maybe we should make it bigger? 😉

from container.

Thanks for the quick reply!

I'll be honest and admit that I didn't read the release notes of version 1.7.0 completely and just followed the relatively simple upgrade guide.
That was actually the reason for my surprise, especially since the other upgrades went through without a hitch. Perhaps a hint there would still be helpful. :)

from container.