Thanks Francis, will modify the upstream server
From: nginx on behalf of Francis Daly
Sent: Wednesday, July 3, 2019 12:22 PM
To: nginx@nginx.org
Subject: Re: Nginx 1.17.0 doesn't change the content-type header
On Wed, Jul 03, 2019 at 06:17:46AM +, A
On Wed, Jul 03, 2019 at 06:17:46AM +, Andrew Andonopoulos wrote:
Hi there,
I think that the point is:
nginx does not change the content-type header from the upstream server.
If you want your nginx to do that, you have to configure your nginx to
do that -- probably using "add_header".
> Ngi
ntent-type is from the default
in the HTTP rather than the location in the Server
Thanks
Andrew
From: nginx on behalf of Maxim Dounin
Sent: Wednesday, July 3, 2019 12:40 AM
To: nginx@nginx.org
Subject: Re: Nginx 1.17.0 doesn't change the content-type hea
Hello!
On Sat, Jun 29, 2019 at 10:49:00PM +, 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
Hello,
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
