See Also
 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
The Web Server supports only a subset of the functionality that is offered by IIS for HTTP header management.
On an SF_NOTIFY_PREPROC_HEADERS flag event, both the AddHeaderand SetHeaderfunctions only modify the method, URI, and HTTP version values in the simple request line.
On an SF_NOTIFY_SEND_RESPONSE flag event, the AddHeaderand SetHeaderfunctions operate differently on the Web Server. On IIS, filters may delete the lpszNamevalue if it has been set to \0 by lpszValueon a call to the SetHeaderor AddHeaderfunction. IIS also allows existing response headers to be overwritten with a call to the SetHeaderfunction, with the new value in lpszValue. The Web Server has no support for either of these options. After a new header name and value pair have been added with the SetHeaderor AddHeaderfunction, it cannot be deleted or overwritten.
When converting headers that are added with the AddHeaderor SetHeaderfunction into raw HTTP headers, the Web Server adds a space between the lpszNameand lspzValuevalues and adds a trailing \r\n to the end of each header pair. However, it does not add a colon to the end of the lpszNamevalue.
 Note: |
|---|
| The Web Server ISAPI filter implementation cannot change the read size of data on POST requests; the read size is fixed at 48 KB. Any block of incoming data that is larger than the read size is read into a buffer. |