如何创建电子邮件回复/方法来编码回复？(How to create email reply / method to code a reply?)

 更整洁优雅的解决方案： 
 
 注意：文件扩展名.gzip似乎很奇怪，一般来说，我们将一个gziped文件命名为.gz ，因此在本例中，如果您坚持使用.gzip ，则使用.gz而不是.gzip ，只需替换以下所有扩展名配置文件。 
 
 
 首先编码，这就是web.config所需的全部内容 
 
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.webServer>
    <staticContent>
      <remove fileExtension=".js.gz" />
      <remove fileExtension=".css.gz" />
      <remove fileExtension=".png.gz" />
      <remove fileExtension=".jpg.gz" />
      <remove fileExtension=".gif.gz" />
      <remove fileExtension=".svg.gz" />
      <remove fileExtension=".html.gz" />
      <remove fileExtension=".json.gz" />
      <mimeMap fileExtension=".js.gz" mimeType="application/javascript" />
      <mimeMap fileExtension=".css.gz" mimeType="text/css" />
      <mimeMap fileExtension=".png.gz" mimeType="image/png" />
      <mimeMap fileExtension=".jpg.gz" mimeType="image/jpeg" />
      <mimeMap fileExtension=".gif.gz" mimeType="image/gif" />
      <mimeMap fileExtension=".svg.gz" mimeType="image/svg+xml" />
      <mimeMap fileExtension=".html.gz" mimeType="text/html" />
      <mimeMap fileExtension=".json.gz" mimeType="application/json" />
    </staticContent>

    <rewrite>
      <outboundRules rewriteBeforeCache="true">
        <rule name="Custom gzip file header">
          <match serverVariable="RESPONSE_CONTENT_ENCODING" pattern=".*" />
          <conditions>
            <add input="{REQUEST_URI}" pattern="\.gz$" />
          </conditions>
          <action type="Rewrite" value="gzip"/>
        </rule>
      </outboundRules>

      <rules>
        <rule name="Rewrite gzip file">
          <match url="(.*)"/>
          <conditions>
            <add input="{HTTP_ACCEPT_ENCODING}" pattern="gzip" />
            <add input="{REQUEST_FILENAME}.gz" matchType="IsFile" />
          </conditions>
          <action type="Rewrite" url="{R:1}.gz" />
        </rule>
      </rules>
    </rewrite>
  </system.webServer>
</configuration>
 
 
 而且，它是如何工作的： 
 
 为了实现成功的gziped数据传输，我们需要： 
 
 
 
 客户端接受gziped数据， Accept-Encoding 
 
 
 带有Content-Encoding的标题响应 
 
 
 正确的MIME类型，原始文件是，但不是application/gzip 
 
 
 Gziped文件 
 
 
 这四个条件必须同时满足。 
 
 如果使用Content-Encoding: gzip发送一个未压缩的文件，浏览器将返回一个错误; 
 
 如果您发送没有Content-Encoding标头或不匹配的MIME类型的压缩文件，页面可能会返回一些Zenith Star的文本。 
 
 所以我们正在做的是： 
 
 
 
 重新定义每种类型的gziped文件的MIME 
 
 
 如果客户端接受gziped文件，则直接将响应文件重定向到服务器端的gziped版本（而不是302/303/307响应） 
 
 
 只有当客户端发送头部Accept-Encoding ， 才重写Content-Encoding响应头的头部 
 
 
 
 这个解决方案适用于我的IIS7，不知道它是否也适用于IIS10。 
 
 如果遇到任何问题，请告诉我：D 

A more neat and elegant solution:
 
NOTICE: The file extension .gzip seems strange, in general, we name a gziped file as .gz, so in this example, we use .gz instead .gzip, if you insist on .gzip, just replace all the extensions in the following config file.
 
 
Code first, this is what all we need for web.config
 
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.webServer>
    <staticContent>
      <remove fileExtension=".js.gz" />
      <remove fileExtension=".css.gz" />
      <remove fileExtension=".png.gz" />
      <remove fileExtension=".jpg.gz" />
      <remove fileExtension=".gif.gz" />
      <remove fileExtension=".svg.gz" />
      <remove fileExtension=".html.gz" />
      <remove fileExtension=".json.gz" />
      <mimeMap fileExtension=".js.gz" mimeType="application/javascript" />
      <mimeMap fileExtension=".css.gz" mimeType="text/css" />
      <mimeMap fileExtension=".png.gz" mimeType="image/png" />
      <mimeMap fileExtension=".jpg.gz" mimeType="image/jpeg" />
      <mimeMap fileExtension=".gif.gz" mimeType="image/gif" />
      <mimeMap fileExtension=".svg.gz" mimeType="image/svg+xml" />
      <mimeMap fileExtension=".html.gz" mimeType="text/html" />
      <mimeMap fileExtension=".json.gz" mimeType="application/json" />
    </staticContent>

    <rewrite>
      <outboundRules rewriteBeforeCache="true">
        <rule name="Custom gzip file header">
          <match serverVariable="RESPONSE_CONTENT_ENCODING" pattern=".*" />
          <conditions>
            <add input="{REQUEST_URI}" pattern="\.gz$" />
          </conditions>
          <action type="Rewrite" value="gzip"/>
        </rule>
      </outboundRules>

      <rules>
        <rule name="Rewrite gzip file">
          <match url="(.*)"/>
          <conditions>
            <add input="{HTTP_ACCEPT_ENCODING}" pattern="gzip" />
            <add input="{REQUEST_FILENAME}.gz" matchType="IsFile" />
          </conditions>
          <action type="Rewrite" url="{R:1}.gz" />
        </rule>
      </rules>
    </rewrite>
  </system.webServer>
</configuration>
 
 
And, here are how it works:
 
In order to achieve a successful gziped data transmission, we need:
 
 
 
Client side accept gziped data, Accept-Encoding
 
 
Response with a header with Content-Encoding
 
 
Proper MIME type, as the original file is, BUT NOT application/gzip
 
 
Gziped file
 
 
The four conditions must be satisfied at the same time.
 
If you send an uncompressed file with Content-Encoding: gzip, the browser will return an error;
 
If you send a compressed file without a Content-Encoding header, or a mismatched MIME type, the page may return some Zenith Star's text.
 
So what we are doing is:
 
 
 
Redefine each type of gziped file's MIME
 
 
If the client side accept a gziped file, then redirect the response file to a gziped version on the server side directly (not 302/303/307 response)
 
 
Rewrite the header of the response header of Content-Encoding, only if the client side send the header Accept-Encoding
 
 
 
This solution works on my IIS7, not sure if it will also work on IIS10.
 
If you met any problem, let me know :D