Well, this is embarrassing. The correct content type is actually application/wasm. (application/webassembly was overruled because Chromium went ahead with the other one.)

https://github.com/WebAssembly/spec/issues/573

Best,
Niklas

On 02.02.2018 16:03, Niklas Fiekas wrote:
Dear maintainers,

please consider adding the application/webassembly content type for wasm files.

With this header recent browsers allow streaming compilation.

Best regards,
Niklas


_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel

# HG changeset patch
# User Niklas Fiekas <niklas.fie...@backscattering.de>
# Date 1517582661 -3600
#      Fri Feb 02 15:44:21 2018 +0100
# Node ID 387929aebb4150d54acc61b56040706c8287fe5e
# Parent  0b72d545f098b407351a1972fba5d29f2e904507
Add application/wasm content type

WebAssembly files with this content type support asynchronous/streaming
compilation.

diff -r 0b72d545f098 -r 387929aebb41 conf/mime.types
--- a/conf/mime.types	Tue Jan 30 22:23:58 2018 +0300
+++ b/conf/mime.types	Fri Feb 02 15:44:21 2018 +0100
@@ -49,6 +49,7 @@
     application/vnd.openxmlformats-officedocument.wordprocessingml.document
                                                      docx;
     application/vnd.wap.wmlc                         wmlc;
+    application/wasm                                 wasm;
     application/x-7z-compressed                      7z;
     application/x-cocoa                              cco;
     application/x-java-archive-diff                  jardiff;
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel

Reply via email to