Setting a custom Content-Type in next.config.js

Question

In the linked commit, I'm setting two headers on requests to the site root, and it's at least partially working since X-Content-Type-Options does appear but Content-Type is being overridden somewhere back to text/html.

https://github.com/toraora/custom-headers-nextjs/commit/06ddd1ef8c95c3fe4cb2dee4ae74f0e85c92f92e

It's documented that this configuration should not be used for Cache-Control, but is there a similar stipulation against using it for Content-Type?

Polar bear · Answer

for what it's worth, this does appear to work in v12.0.10https://github.com/toraora/custom-headers-nextjs/commit/e8d1780c54e29fb4a32dd3995cb3e1bc9547178d

Setting a custom Content-Type in next.config.js

1 Reply