We'd love to hear about it! Click here to go to the product suggestion community
My question – what am I doing wrong about site path routing setup? Is what I am trying to do achievable?
Hi Ascar Omarov
I would suggest you go through this Recommended Read article Sophos UTM: Securing Web Application Firewall (WAF) and refer Path management and URL hardening. That should help you with your configuration.
Hello Ascar,Please consider, you need the path called at the virtual web server (https://www.abc.com/commerce) at the real webserver too.(commerce.abc.com/commerce )
In reply to dirkkotte:
Thanks for suggestion.
Do you mean a separate path route should be set up in UTM or you mean on the real webserver https://commerce.abc.com I should have a folder under the site root like application_folder/commerce? I am confused.
I tried adding a folder 'commerce' inside the application folder which should not have any impact and it did not other than throwing a 403 Error since there is no default document in the folder.
If you mean that it should be a site path route in UTM then I don't know how to do it.
site 1: https://www.abc.com should hit the default page of the site 1
site 1: https://www.abc.com/commerce should open the default page of the site 2 in the context path of site 1
So, what kind of route should I write for https://commerce.abc.com ?
In reply to Ascar Omarov:
I made an additional path route which looks like this
Virtual Web Server: https://commerce.abc.com
Real Web Server: Real Webserver for Virtual Server 2
However I still get the same 404 errors, so my source server (Webserver 1) is still trying to locate an non-existent folder in its file system, which I believe, means site path routing instruction has no effect on Webserver 1. What do you think?
with Path: /commerce --> Real WebServer 2 the Webserver 1 should not show you access.
Please give us some screenshots from virtual ws, real ws and sitepath settings.