Skip to content

[Bug]: jekyll serve sets the wrong content type for .wasm files #8936

@daveyarwood

Description

@daveyarwood

Operating System

Ubuntu 20.04

Ruby Version

ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux]

Jekyll Version

jekyll 4.2.1

GitHub Pages Version

N/A. The issue occurs when serving my site locally via bundle exec jekyll serve.

Expected Behavior

When serving a site with jekyll serve, asset files with the extension .wasm should be served with the Content-Type application/wasm.

IMPORTANT: It can't be application/wasm; charset=utf-8! It needs to be application/wasm in order for WebAssembly to work.

Current Behavior

At the moment, I'm seeing the Content-Type of the .wasm asset coming back as application/wasm; charset=utf-8.

IIRC, earlier, it was coming back as text/html; charset=utf-8, which is even worse. I've been tinkering locally, so it's possible that I've halfway fixed it to return application/wasm; charset=utf-8, but even so, it seems like something deep in the internals of Jekyll or WEBrick is automatically adding the ;charset=utf-8 part.

NOTE: This issue was originally raised 3 years ago: #7743 but there was no response and your bot automatically closed it as stale after 5 months. The problem persists, though. Please don't close this without responding!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions