# 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:** 17

<div class="post-metadata">

**Author:** ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)\
**Post date:** [January 3, 2025, 12:01pm UTC](https://meta.discourse.org/t/incorrect-mime-types-content-type-header-for-mp4-and-js/257802/17 "2025-01-03T12:01:00Z")

</div>

Not sure I fully understand, so quick question about this PR 🙋

Why do the modifications specifically target s3-related files, when the forced download occurs even when not using s3? 🤔

Will it fix the issue in general anyway?  
Will it also fix forced download for other files that could be opened in the browser such as PDFs?

---

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