mirror of https://github.com/TriliumNext/Notes
refactor(cookiePath): remove non-working cookiePath option
this option will currently not work => the cookie will never be set by the server, if you use a different path other than "/" in order for this to work we would need to introduce some kind of "custom route prefix", that would make express serve the routes with the custom prefix — but that kinda falls more into a reverse proxy job territory. So let's remove this feature for now and amend the docs on how to correctly handle the cookies per instance via the reverse proxy.pull/1686/head
parent
78778305ff
commit
a979e87a7f
Loading…
Reference in New Issue