[issue35403] support application/wasm in mimetypes and http.server

Change by Martin Panter : -- superseder: -> http.server module sets incorrect mimetype for WebAssembly files ___ Python tracker ___

[issue35403] support application/wasm in mimetypes and http.server

Martin Panter added the comment: According to Issue 34758, this was already added to 3.8’s “mimetypes”. -- nosy: +martin.panter resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue35403] support application/wasm in mimetypes and http.server

pmpp added the comment: Sure, but i was considering the cpython in the browser/webview/electron case where python modules are served as .wasm files, i'm about to do it for my port and pyodide already does. It would make sense to provide the *simplest* environnement for cpython to serve its

[issue35403] support application/wasm in mimetypes and http.server

R. David Murray added the comment: We don't generally add a mime type until it is a de-jure or de-facto standard. If it is still in testing it is probably too soon to add it. For testing, you can always add it yourself in your code via the api that mimetypes provides. --

[issue35403] support application/wasm in mimetypes and http.server

Change by Terry J. Reedy : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35403] support application/wasm in mimetypes and http.server

Steven D'Aprano added the comment: Python 3.7 is in feature-freeze, so any new features like this will have to be 3.8 only. -- nosy: +steven.daprano versions: -Python 3.7 ___ Python tracker

[issue35403] support application/wasm in mimetypes and http.server

New submission from pmpp : web browsers have recently gained ability to run webassembly code and for that a new content type has to be add to web servers for optimal use: wasm => Content-Type header : application/wasm spec says it :