Nginx 1.17.0 doesn't change the content-type header
Maxim Dounin
mdounin at mdounin.ru
Wed Jul 3 00:40:43 UTC 2019
Hello!
On Sat, Jun 29, 2019 at 10:49:00PM +0000, Andrew Andonopoulos wrote:
> I have the following config in the http:
>
> include mime.types;
> default_type application/octet-stream;
>
>
> also i have this in the location:
>
> types {
> application/vnd.apple.mpegurl m3u8;
> video/mp2t ts;
> }
>
>
> But when i send a request, i am getting these headers:
>
> Request URL:
> https://example.com/hls/5d134afe91b970.80939375/1024_576_1500_5d134afe91b970.80939375_00169.ts
[...]
> ETag:
> "7ba4b759c57dbffbca650ce6a290f524"
[...]
> For some reason, Nginx doesn't change the Content-Type
The ETag header format suggests that the response is not returned
by nginx, but rather by a backend server. Check your backend
server.
--
Maxim Dounin
http://mdounin.ru/
More information about the nginx
mailing list