Update.
I entered the Docker container, thinking that I could use some Nginx trickery to accomplish this. Nginx has what looks like a perfect directive to handle this: proxy_cookie_domain
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_cookie_domain
But, as usual, Nginx is a tricky trickster. This only works if there is a ;domain= set in the cookie.
But the set-cookie headers coming back from discourse are sans domain. For instance
set-cookie:_forum_session=d2tpcUFWbHB0TXV4KzlzMWdTcnR4Z0U3UjNUN1FJRGdtTHdLRU1BYlN1N3dRNkFGK0d3dVNja2o3bHBvZHYzQ2NWSUdVMm9COFhCSjBzSTJIVThoOEdSdWFZMk9ucFhSVitWc0J3WCswdFNTMTJpYmZTSVR4K2JlT0xnaHNseEIvcDRub3Rla0FGZjNZMnVsWkhTbHVQSFRQSkVaUXZWTkxhQjNGUnBNM3didDkrMFFEV0M2OEdWQndlWWhvTXVmLS0wZkhMOGtmRGhjYXBOcnlqQzVVdzR3PT0%3D--036dcfb2a44bce0fafade7a2c46dd2b4e5e7b2fe; path=/two; HttpOnly
You can see in the above that I was able to use a proxy_cookie_path to change the path from ‘/’ to ‘/two’, but the lack of domain in the set-cookie does not allow me to do this in Nginx.
Can anyone point me to the ruby file that sets the cookie? I’ve scanned github and used find/xargs/grep like crazy on the source but can’t seem to find where this is being set.
daniel