Community mailing list archives

AW: AW: 404 when getting CSS for qweb report

- 05/05/2016 09:21:01

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 ;-)




Von: Alexandre Fayolle []
Gesendet: Donnerstag, 05. Mai 2016 15:13
An: Community <>
Betreff: Re: AW: 404 when getting CSS for qweb report


Thanks, but this has nothing to do with web.base.url and report.url.


Digging further, it appears that this one report for some weird reason

cause wkhtmltopdf to query back Odoo without specifying a database. This

makes the /web/content route unavailable, and produces a 404.


I'm currently investigating why this report is behaving in such a

strange way.