Hello,
I’m currently evaluating IISBrotli V2.0 on IIS 10. The initial test however shows that the module isn’t effective. Testing with latest version of Chrome, I see “accept-encoding: gzip, deflate, br” in the request’s header and “content-encoding: deflate” in response.
I assumed this might have something to do with the order of encodings in the request. So I tried cUrl:
curl -s -o /dev/null -ikv -H "accept-encoding: br" https://my_url_to_js_file
And the response indicated that we’re still using “deflate”:
< HTTP/2 200
< cache-control: public
< content-type: application/javascript
< content-encoding: deflate
< server: Microsoft-IIS/10.0
< date: Tue, 26 Feb 2019 23:29:17 GMT
I even edited IIS’s applicationHost file to list “IISBrotli” as the first module in case that matters. Moreover, added a compression scheme for “br”:
<httpCompression directory="%SystemDrive%\inetpub\temp\IIS Temporary Compressed Files">
<scheme name="br" dll="%ProgramFiles%\We-Amp\IISBrotli\IISBrotli.dll" staticCompressionLevel="11" />
<scheme name="gzip" dll="%Windir%\system32\inetsrv\gzip.dll" staticCompressionLevel="9" />
<staticTypes>
<add mimeType="text/*" enabled="true" />
<add mimeType="message/*" enabled="true" />
<add mimeType="application/javascript" enabled="true" />
<add mimeType="application/atom+xml" enabled="true" />
<add mimeType="application/xaml+xml" enabled="true" />
<add mimeType="image/svg+xml" enabled="true" />
<add mimeType="*/*" enabled="false" />
</staticTypes>
</httpCompression>
It’s worth mentioning that I restart IIS with every change I make.
None of these changes have made the module work. I wonder if there is anything else I need to configure.
Thanks,
Amir