[18.0][FIX] dbs value has to be kept in case of special proxy config - #3694
[18.0][FIX] dbs value has to be kept in case of special proxy config#3694ivilata wants to merge 1 commit into
Conversation
|
@thomaspaulb @hbrunn, you may want to review/approve this direct port from @cvinh's #2828, as you did for 16.0. Thanks! |
hbrunn
left a comment
There was a problem hiding this comment.
reexamining this, it's actually quite a radical change that in any case makes
Please keep in mind that the standard odoo dbfilter configuration is still applied before looking at the regular expression in the header.
from the readme false. So please update that too. And stress that it's super relevant to set the header everywhere.
Without this patch, you can set dbfilter = ^db1|db2|db3$ and be sure this Odoo instance will only ever be able to access those three dbs. With the patch, whenever one has access to the unproxied instance or one that doesn't set the header, you can pass whatever other database that's accessible to the database user, which might be an issue for some deployments.
So actually, I'm not sure any more I agree with this patch.
|
Thanks @hbrunn for the heads up and sorry for the noise, I failed to check if there was an existing PR for this. Since #3475 is already from the original author, I'll retract this PR to avoid dispersing the discussions as well. I'll copy your comment there so that people don't need to jump too much among PRs. 🙂 |
Ported from #2828 using
oca-port.