Fortiweb " was not found on this server".

[alizares93]

Hello
I have the following issue.
I need to do a routing by http content with fortiweb, as an example
www.informacion.go.rx/vista/1_inicio
I have already made the policy in which when it finds www.informacion.go.rx it redirects to the server 10.22.130.5 through port 80.
The problem I have is that it is not finding the URL /vista on the web server since vista is located in the following route
10.22.130.5/www/vista.
In nginx as a proxy server I can add a specific route
in the proxy "proxy_pass" from where to start looking for the URL, but in fortiweb I have not been able to find it.
I hope you can help me to see if there is a way to do the same in Fortiweb

[AEK]

Hello

If I'm not misunderstanding your requirement, you need to create a URL Rewriting policy.

https://docs.fortinet.com/document/fortiweb/7.6.0/administration-guide/961303/rewriting-redirecting

While I personally try avoid it as much as I can, by making the required change directly on the back-end Web server.

[alizares93]

Hello, look, the problem is the following, because of how the web application is developed, the www/ is hidden.
Since it is behind a reverse proxy with nginx, when sending the request to the web server, it sends it to the address 10.22.55.2/www and I have noticed in fortiweb I have noticed that in fortiweb I have not seen where I can define in the pool server something similar as in nginx
I hope you can help me.

[AEK]

Hello Ali

In FortiWeb it is different. Such operation is not performed at pool level but you can do it via URL rewriting policy/rule.

The idea is to change any request from client like server/anything, to server/www/anything, before send it to the back-end server. URL rewriting policy can do this among other things.

[alizares93]

Hi, sorry for not responding. I tried to rewrite it but it didn't work. Do you have any material or examples that could help me with the implementation

[AEK]

Hello

https://help.fortinet.com/fweb/573/Content/FortiWeb/fortiweb-admin/application_delivery.htm

Hope it helps.

I didn't configure such since a couple of months, but basically the "Request Type" should be "Request Action", then you replace the requested URL by the back-end URL.

And you need to make few tests in order to tune it for your exact need.