IE will display their own error page if your error response is smaller
than a certain size; however, AFAIK that's triggered by size, not
request method.
What is the status code and content-type you're sending back?
Cheers,
On 22/07/2008, at 7:56 AM, Michael Kaplan wrote:
> Hi,
>
> I am trying to filter POST messages seen in Squid that do not follow
> my application specifications. When a POST is observed that misuses
> the header, I would like to send a a custom error page to the host
> which would be displayed in the browser. I've added the appropriate
> enumeration for the error page as well as the error page definition
> within Squid. I then added code to the clientProcessRequest
> function in client_side.cc to detect the erroneous POST, and then
> followed the convention of generating reply context, set reply to
> error, etc. Using Wireshark, I was able to verify that the error
> page was indeed sent to the host, however, IE just displayed a
> default error page, not showing the custom error page that I
> generated.
>
> Interestingly if i change my code to react to GET instead of POST,
> my custom error page DOES display properly. So I'm wondering if it
> is an issue with the POST protocol. Perhaps IE is not expecting HTML
> in response to a POST?
>
> Has anyone encountered or tried such a thing?
>
> Thanks,
> Mike
-- Mark Nottingham mnot_at_yahoo-inc.comReceived on Tue Jul 22 2008 - 19:08:57 MDT
This archive was generated by hypermail 2.2.0 : Wed Jul 23 2008 - 12:00:07 MDT