You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
dbadmin page is accessible at this public url https://example.com/dbadmin
in a private network it is hosted on https://private_domain.com/dbadmin
there a reverse proxy mapping /dbadmin* path to private_domain/dbadmin*
In this case only the dynamic resources are accessible but not static ones.
Indeed it's trying to load script like this one https://example.com/js/table.js which is not accessible as only dbadmin is mapped with the reverse proxy.
This is PR trying to fix with a configuration properties: #15
But it can be solved also by reusing by default dbadmin_baseUrl on static resources.
The text was updated successfully, but these errors were encountered:
I've pushed two commits (31200ad, ec7eac3) to the dev branch which should fix this. I haven't replicated the full setup with the reverse proxy, but I've verified that static resources are now served under /${dbadmin_baseUrl} and referenced as such in the HTML template.
Can you try by any chance or look at the two commits? I believe this is correct.
Describe the bug
dbadmin page is accessible at this public url https://example.com/dbadmin
in a private network it is hosted on https://private_domain.com/dbadmin
there a reverse proxy mapping /dbadmin* path to private_domain/dbadmin*
In this case only the dynamic resources are accessible but not static ones.
Indeed it's trying to load script like this one https://example.com/js/table.js which is not accessible as only dbadmin is mapped with the reverse proxy.
This is PR trying to fix with a configuration properties: #15
But it can be solved also by reusing by default dbadmin_baseUrl on static resources.
The text was updated successfully, but these errors were encountered: