I have a webservice that I am trying to put behind a WAF on XG 18. Internally the service is plaintext on port 10031. Externally it's available via HTTPS on port 443. Connecting to the site externally has you visiting https://webservicename.domain.com/web/services/cj_get_orders/20210305. An authentication window is supposed to pop up, and after successful authentication it should push a JSON file to your client with a name corresponding with the date 'directory' in the path. The 20210305 can be any date (yyyymmdd).
On XG 18.04 I have the WAF configured with the external port alias, listening port 443/HTTPS, certificate applied, domain is set as webservicename.domain.com. With Path-specific routing turned off, trying to visit the /web/services/cj_get_orders/ gives a 403 Forbidden response.
If I turn path-specific routing on and create a path of /web/services/cj_get_orders/ and then visit https://webservicename.domain.com/web/services/cj_get_orders/20210305 I will get the authentication box. If I successfully authenticate I will get a 404 Not Found response.
Since I'm at the 'grasping at straws' point, I've experimented with Rewrite HTML, have tried a path specific routing including the 20210305, tried eliminating the WAF and doing a straight DNAT with port translation from 443 to 10031 (I believe I built this incorrectly and will probably try again).
We migrated from UTM last Saturday and have a number of these smaller issues that we're working through. Any help is greatly appreciated. Thanks in advance--GD
This thread was automatically locked due to age.
