XML Gateway handling of http 302 redirection

[l3leong3990]

My application server sends an http 302 redirection response back to the web browser along with the URL for redirection.  The redirection works when testing without the XML Gateway between the browser and the application server, but with the XML Gateway sitting in the middle, the XML Gateway intercepts the http 302 and tries to perform the redirection from inside the DMZ (rather than letting the browser do it from the "outside").  This causes an error because the URL in the redirection has an internet address which is not resolvable from inside the DMZ.  It there a way to let the http 302 response pass through the XML Gateway to the browser without having the XML Gateway act on the redirection?                

[l3leong3990]

I'll answer my own question here.  Found the section in the XML User Guide about mapping HTTP Error Responses (chapter 22 in the v6.1 pdf) and realized that the XML gateway had preconfigured settings to handle various error conditions.  Edited the error handling configuration for the specific Handler (rather than the global setting) and checked the box to allow the error to pass through the XML gateway.  Redeployed the subpolicy.