So, as discussed with @RReverser and @arai on another channel, we could use - `Content-Type=application/javascript-binast` (current version – for backwards compatibility, that's the multipart encoding) - `Content-Type=application/javascript-binast;encoding=x-multipart` (experimental, multipart) - `Content-Type=application/javascript-binast;encoding=context-0.1` (experimental, context 0.1) - etc. Not sure if we can somehow register every content type that starts with `application/javascript-binast`.
Bug 1519080 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
So, as discussed with @RReverser and @arai on another channel, we could use - `Content-Type=application/javascript-binast` (current version – for backwards compatibility, that's the multipart encoding) - `Content-Type=application/javascript-binast;encoding=x-multipart` (experimental, multipart) - `Content-Type=application/javascript-binast;encoding=context-0.1` (experimental, context 0.1) - etc. and use `Content-Encoding=br` (or other). Not sure if we can somehow register every content type that starts with `application/javascript-binast`.