The 403 HTTP code:
On the other hand, in the RFC2616, the codes HTTP 403 can contain a message
to indicate information to the user. The SQUID on code 403 does not respect
the RFC. It posts an SQUID error message (connexion failed) without
checking that the request contains a message for the user. Can I change
this behavior?
The other exemple:
the page returned by IWSS when a virus is intercepted is not forwarded with
the customer. This page is turned over with a code 403. The squid sends
this error page: "connection failed".
This page normaly sended to IWSS is :
HTTP/1.1 403 Forbidden
Connection: close
Date: Wed, 03 Nov, 2004 08:47:15 GMT
Cache-Control: no-cache
Content-Type: text/html; charset=UTF-8
Server: Version 2.0-Build_Linux_1280 $Date: 08/17/2004 18:15:0038$
Content-Length: 810
<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html;
charset=UTF-8"/><title>IWSS Security Event</title>
</head>
<body>
<script> if( typeof( window.innerWidth ) == 'number' ) {if
(window.innerWidth < 10 || window.innerHeight < 10)
{self.resizeTo(700,600);}}else if (document.body &&
(document.body.clientWidth < 10 || document.body.clientHeight < 10))
{self.resizeTo(700, 600);}
</script>
<h1><h1>IWSS Security Event (proxyicap)</h1></h1>Access to this URL
is currently restricted due to a blocking rule.<BR><BR>URL:
<B>http://netcourrier-4m.netcourrier.com/mnet-MAIL.fr/NjA4LhAP9nCQY1gFXHbbHPHk4ig/Read.14/attach/1-.xx.pif</B><BR>Rule:
Block URLs of type <B>Virus infected temporary block</B><P>If you feel you
have reached this message in error, please contact your network
administrator.
</body>
</html>
Thank you.
Received on Wed Oct 13 2004 - 03:56:26 MDT
This archive was generated by hypermail pre-2.1.9 : Mon Nov 01 2004 - 12:00:02 MST