On 1/2/25 0:24, Marc wrote:
I have a config and actually only want to allow access to a specific path xxx of the proxied host nothing else. However that path on the proxied host is refering to files eg in the root ProxyPreserveHost Off ProxyAddHeaders On SetOutputFilter proxy-html ProxyHTMLEnable On ProxyHTMLExtended On ProxyPass "https://${proxyhost}/xxx"; ProxyPassReverse "https://${proxyhost}/xxx"; ProxyHTMLURLMap https://${proxyhost}/xxx https://${defaulthost}/aaa I have such references to the proxied host in the website pages, links suchs as these: <script src="https://proxyhost/js/";></script><script src="https://proxyhost/js/....s";></script><script src="https://proxyhost/js/.....js";></script><script src="https://proxyhost/js/..js";></script><script src="https://proxyhost/js/l....js";></script><script src="https://proxyhost/js/....";></script> Any ideas what what would be a good method to handle these exceptions outside of the xxx path?Is it correct that this does not work? <LocationMatch /../xxxx> ProxyPass "https://aaaa"; ProxyPassReverse "https://aaaa"; </LocationMatch> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
I would generally try to set ProxyPreserveHost on and see how the backend reacts before trying to change every entry it sends with a hostname instead of a relative link --- Daniel Help at #httpd in Libera.chat --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|