When the Microsoft FrontPage or the Web Folders client technologies issue an HTTP GET
request to the FrontPage Smart HTML Interpreter DLL, the Shtml.dll file, on a Web server where there are not any ISAPI filters configured, the raw
HTTP response may be similar to the following example:
HTTP/1.1 200 OK{CRLF}
Server: Microsoft-IIS/5.0{CRLF}
Date: Sun, 1 Jan 2000 12:00:00 GMT{CRLF}
MicrosoftOfficeWebServer: 5.0_Pub{CRLF}
Connection: close{CRLF}
Content-Type: text/html; charset=windows-1252{CRLF}
{CRLF}
<HTML><BODY>Cannot run the FrontPage Server
Extensions on this page: ""</BODY></HTML>
In this
example, the server returns several headers to the client, including
the
Server type (in this scenario,
Microsoft-IIS/5.0 is the
Server type header that is returned) and the
Date. The end-of-header marker is the blank line where only the
carriage-return line-feed (CRLF) characters are present.
When you install an ISAPI
filter that modifies the server headers in combination with SharePoint Team
Services or the FrontPage Server Extensions, an extra end-of-header marker is
inserted, and you receive the error message that is mentioned in the "Symptoms" section of this
article.
In the following example, the URLScan utility has been
configured to modify the server header to return a non-existent
TEST/1.0 server type instead of the default
Microsoft-IIS/5.0 server type:
HTTP/1.1 200 OK{CRLF}
Date: Sun, 1 Jan 2000 12:00:00 GMT{CRLF}
MicrosoftOfficeWebServer: 5.0_Pub{CRLF}
Connection: close{CRLF}
Server: TEST/1.0{CRLF}
{CRLF}
Content-Type: text/html; charset=windows-1252{CRLF}
{CRLF}
<HTML><BODY>Cannot run the FrontPage Server
Extensions on this page: ""</BODY></HTML>
In the first example in this section, the server header is followed by a blank line that contains only the
CRLF characters, signifying the end of the headers, and this is followed
by another server header from the FrontPage Smart HTML Interpreter DLL, the shtml.dll file. The FrontPage Smart HTML Interpreter DLL, the shtml.dll file, overrides the default content type. Because this
information is returned after a blank line that contains only the
CRLF characters, it is considered to be part of the body of the HTTP
data stream instead of part of the headers. Because of this situation, the FrontPage client cannot
correctly process the response, and you receive the error message that is mentioned in the "Symptoms"
section of this article.