# Incorrect mime-types (content-type header) for mp4 and js

**URL:** <https://meta.discourse.org/t/incorrect-mime-types-content-type-header-for-mp4-and-js/257802>\
**Category:** Bug\
**Created:** [March 11, 2023, 3:27pm UTC](https://meta.discourse.org/t/incorrect-mime-types-content-type-header-for-mp4-and-js/257802 "2023-03-11T15:27:21Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![iprok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/iprok/32/297510_2.png) [@iprok](https://meta.discourse.org/u/iprok)\
**Post date:** [March 14, 2023, 5:09pm UTC](https://meta.discourse.org/t/incorrect-mime-types-content-type-header-for-mp4-and-js/257802/11 "2023-03-14T17:09:30Z")

</div>

In short words discourse sends javascript from different location with different mime-types. E.g. /theme-javascripts/ff3c633d0d4192c83a194066eaa9d823b5c2d8f6.js goes with text/javascript (correct) and previously mentioned /brotli\_asset/… with application/javascript. It can confuse proxy servers between discourse and client so as analytic systems, where I have noticed the issue.

Seems you just need to correctly setup internal nginx in discourse docker image for brotli assets.

---

_[View the full topic](https://meta.discourse.org/t/incorrect-mime-types-content-type-header-for-mp4-and-js/257802)._