Community mailing list archives
AW: AW: 404 when getting CSS for qweb reportby
It could have to do with this (if the protocols are different for the outside and inside view for example) but you are right…the 404 is probably b/c of the unavailable route or resource.
Anyway, I confirm that the report is calling the CSS/JS from the report generation itself like you expect it when it is rendered just in time.
So, interested what you will find out yourself…I think the cookie domain and session is not completely unrelated, but you have to find out for your current issue locally ;-)