Is it possible to stop the MAG-only appliance from taking over errors being vended up by the origin webservers?
With old iChain and the current 3.1 SP4 and prior LAGs, if the back-end webservers defined for any given Proxy Service themselves encounter an a problem -- say, 404 Not Found -- the web server's own error pages are vended to the browser.
Now, with the MAG-only appliance, those same 404 Not Found errors are totally intercepted by the MAG and its own pages are sent by default.
This is completely unwanted behavior. We have over 100+ websites configured through NAM. There are a wide variety of audiences who access NAM who never visit the same resources and the way we communicate with each of them is different.
As such, most of the webservers vend their own (and sometimes very elaborate) error re-branding that they want to show to customers, or to vendors/suppliers, or to employees. Different contact details are provided on a per-site basis.
That branding and verbiage changes too often, on a site by site basis, for me to try and re-create it with complex "if site = this" type control statements inside the MAG's error page templates.
Bottom line: we need a way to disable this "feature" of the MAG, so that it only displays its OWN errors and does not intrusively try to take over others served up by the webservers it protects.
If this can't be disabled, it may become a deal-breaker for us. Our marketing and other similar departments would throw a fit if we moved their sites behind this...
- Stefan
With old iChain and the current 3.1 SP4 and prior LAGs, if the back-end webservers defined for any given Proxy Service themselves encounter an a problem -- say, 404 Not Found -- the web server's own error pages are vended to the browser.
Now, with the MAG-only appliance, those same 404 Not Found errors are totally intercepted by the MAG and its own pages are sent by default.
This is completely unwanted behavior. We have over 100+ websites configured through NAM. There are a wide variety of audiences who access NAM who never visit the same resources and the way we communicate with each of them is different.
As such, most of the webservers vend their own (and sometimes very elaborate) error re-branding that they want to show to customers, or to vendors/suppliers, or to employees. Different contact details are provided on a per-site basis.
That branding and verbiage changes too often, on a site by site basis, for me to try and re-create it with complex "if site = this" type control statements inside the MAG's error page templates.
Bottom line: we need a way to disable this "feature" of the MAG, so that it only displays its OWN errors and does not intrusively try to take over others served up by the webservers it protects.
If this can't be disabled, it may become a deal-breaker for us. Our marketing and other similar departments would throw a fit if we moved their sites behind this...
- Stefan