We have an ISAPI module and filter that inspects and modifies responses. We have this scenario where Firefox with HTTP2 enabled sends a request that fails within IIS, and a second request is immediately re-introduced into the pipeline (perhaps resent from the Firefox client). The two requests are very similar except the first one had TE: trailer header and connection:close. When looking at the Failed Request Trace, we see that the flush on the first request fails with 'the parameter is incorrect' (below). Is there a way to track down more information on why the flush failed? I tried to track it down within the managed pipeline but wasn't able to - it seems it may be occurring within native code, or maybe a communication error back to the client(?). If Firefox has HTTP2 disabled, the flush error doesn't occur. If we don't have the ISAPI module and filter, the first request succeeds.
0 ms Verbose GENERAL_RESPONSE_ENTITY_BUFFER Buffer HTTP/1.1 302 Found Content-Length: 192 Content-Type: text/html; charset=utf-8 Location: https://SERVER-NAME/VDIR/PATH/FILE.aspx?url=https%3a%2f%2fSERVER-NAME%2fVDIR Server: Microsoft-IIS/10.0 request-id: b8945a72-543a-4474-9837-9420b3176c5b X-Powered-By: ASP.NET X-X-Server: SERVER-NAME <html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="https://SERVER-NAME/VDIR/PATH/FILE.aspx?url=https%3a%2f%2fSERVER-NAME%2fVDIR">here</a>.</h2> </body></html> 0 ms Informational GENERAL_FLUSH_RESPONSE_END BytesSent 0 ErrorCode The parameter is incorrect. (0x80070057) 0 ms GENERAL_REQUEST_END BytesSent 0 BytesReceived 733 HttpStatus 302 HttpSubStatus 0 ```
User contributions licensed under CC BY-SA 3.0