I used to write a URL detection redirection session intrusion detection automatic decompression automatic decryption ISAPI Filter, which has been very good, recently upgraded to Widnows 2003 IIS6 After .0, ISAPI Filter is found to be running at all, then check and check it, it is the privilege problem of the document, IIS 6.0 isapi filter seems to be running under the service account (I didn't check it), will data After the read and write permission of the file, ISAPI Filter finally runs normally, but in subsequent tests, I found that the data decryption results are not correct, depressed, check it ...... .
After log tracking and analysis, I finally found that IIS 6.0 and IIS 5.0 are sent to the client, IIS 5.0 is a single answer to HttpFilterProc-> OnsendData,
HTTDATE: MON, 04 APR 2005 05:39:01 gmtcontent-type: application / ocT-streslast-modified: byteslast-modified: Mon, 04 Apr 2005 05:39:00 GMTETAG: W / "90C9399AD838C51: FD1" Content-Length: 661442
Then send data from multiple times multiple times.
IIS6.0 is sent together the response and data, that is, the first httpfilterproc-> OnsendData, the first httpfilterproc-> ONSENDDATA, also contains data.
HTTP / 1.1 200 Okdate: MON, 04 APR 2005 05:17:09 Gmtcontent-Length: 661442Content-Type: Application / Pdflast-Modified: Mon, 04 APR 2005 05:16:41 Gmtaccept-Ranges: Bytesetag: "4C949B7CD538C51: EF5 "Server: Microsoft-IIS / 6.0x-Powered-by: ASP.NET
% PDUTV? In > 2fw [[; E? V0f [z4 楽 = z; ujvycyx (| XES enemy?
The original procedure did not design it for this situation. After adjustment, ISAPI Filter has successfully runned in IIS 5.0 and IIS 6.0.
