Re: URL filtering using LSP
- From: "Alexander Nickolov" <agnickolov@xxxxxxxx>
- Date: Thu, 27 Sep 2007 16:03:30 -0700
Ideally you should be returning a 403 Forbidden HTTP reponse
instead of closing the socket. This will let the browser properly
display a page with the Forbidden message. You can return an
HTML page with 403 and the browser will display it.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
<andy.y.huang@xxxxxxxxx> wrote in message
news:1190921236.771571.193040@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I am trying to do outbound URL filtering using LSP, basically I
check outbound HTTP request from WSPSend and if I find the URL that
needs to be blocked, then I call WSPCloseSocket and return the error
code from that call, that works fine with Firefox, but for IE, it
will display "Internet Explorer cannot display the webpage". Is it
possible not showing this page after blocking and still shows the
previous page?
Anything I should change in the code, such as return different error
code, set
lpErrno parameter to specific Winsock error code? TIA.
.
- Follow-Ups:
- Re: URL filtering using LSP
- From: andy.y.huang@xxxxxxxxx
- Re: URL filtering using LSP
- References:
- URL filtering using LSP
- From: andy.y.huang@xxxxxxxxx
- URL filtering using LSP
- Prev by Date: URL filtering using LSP
- Next by Date: Re: Problems using UNC address
- Previous by thread: URL filtering using LSP
- Next by thread: Re: URL filtering using LSP
- Index(es):
Relevant Pages
|
|
