Forum Discussion
CirrostratusXC HTTP loadbalancer returns "WAF like" error page even if WAF is disabled
Hi,
I have been testing XC HTTP LB and I noticed that when service responds 403 I dont get original message, but something what looks like WAF error page, even with support id. When I try to search for support ID in XC console I fail, it is not there. Can somebody explain what is behind this, is HTTP LB pro-actively replacing non 2xx responses? And where I can find that support ID related log?
Thanks
The most likely scenario is your origin is returning a 403. By default, an XC loadbalancer will return it's own error page when the response is a non 2xx or 3xx code. You can change that on your LB here:
Check the "Disable Default Error Pages" box and you'll receive the response the origin is returning.
Note that you can also write your own custom error responses for the LB to return. This is useful when you have several different origins in use (maybe based on different routes) and you want to present unified responses.
- Kevin_Reynolds
Employee
The most likely scenario is your origin is returning a 403. By default, an XC loadbalancer will return it's own error page when the response is a non 2xx or 3xx code. You can change that on your LB here:
Check the "Disable Default Error Pages" box and you'll receive the response the origin is returning.
Note that you can also write your own custom error responses for the LB to return. This is useful when you have several different origins in use (maybe based on different routes) and you want to present unified responses.
ZdenekIt was XC LB and its default error response, check my picture, there is F5 site name in it.
Anyway I have disabled default error pages as you advised and it works. I am just bit surprised this is default behavior....
Thanks