Moved from Home to Business > Web Gateway for better support.
No. this cannot be done.
MWG will only respond with a 403 back to the client when something is detected.
It will not alter the contents and forward the body to the server with a dummy file.
The only thing you can do is write client side code that detects the 403 and presents the user with some message within the framework of your application.
If this is for a home-grown web application, you might be better off writing an ICAP client into the application that does the file submission and business logic to accomodate what you are looking for.
Our webserver s not receving any error codes like 403 from MWG. We just see browser hanges with spinnng wheel and never closes session and we need to kill the browser.
Yes. That is the way it works when using a reverse proxy.
All content is blocked from going forward into the web server and the 403 is sent back to the client.
The Ajax routines need to expose the 403 status code into some sort of readable message for the user.