Nginx 1.17.0 doesn't change the content-type header

[Andrew Andonopoulos]

Hello,

I missed the cache status header in my previous email.

This is another response with all the headers:

https://example.com/hls/5d0f9398852b84.49917460/1280_720_1300_5d0f9398852b84.49917460_00004.ts<https://cdn1.cdnlotus.com/hls/5d0f9398852b84.49917460/1280_720_1300_5d0f9398852b84.49917460_00004.ts>


  1.
Accept-Ranges:
bytes
  2.
Access-Control-Allow-Credentials:
true
  3.
Access-Control-Allow-Headers:
DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Origin,X-Auth-Token,Authorization,Accept,Client-Security-Token
  4.
Access-Control-Allow-Methods:
OPTIONS, GET
  5.
Access-Control-Allow-Origin:
*
  6.
Cache-Control:
max-age=31536000
  7.
Connection:
keep-alive
  8.
Content-Length:
114304
  9.
Content-Type:
application/octet-stream
  10.
Date:
Wed, 03 Jul 2019 06:15:02 GMT
  11.
ETag:
"1b744341828e22daea781982614ffc74"
  12.
Last-Modified:
Mon, 24 Jun 2019 22:24:35 GMT
  13.
Server:
nginx/1.17.0
  14.
X-Cache-Status:
HIT
  15.
X-Proxy-Cache:
HIT

<https://cdn1.cdnlotus.com/hls/5d0f9398852b84.49917460/1280_720_1300_5d0f9398852b84.49917460_00004.ts>
Nginx deliver the file from the cache but the content-type is from the default in the HTTP rather than the location in the Server


Thanks
Andrew
________________________________
From: nginx <nginx-bounces at nginx.org> on behalf of Maxim Dounin <mdounin at mdounin.ru>
Sent: Wednesday, July 3, 2019 12:40 AM
To: nginx at nginx.org
Subject: Re: Nginx 1.17.0 doesn't change the content-type header

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/
_______________________________________________
nginx mailing list
nginx at nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20190703/bf259c89/attachment.html>