X-Accel-Redirect and Content-Type
mdounin at mdounin.ru
Fri Nov 5 02:20:47 MSK 2010
On Thu, Nov 04, 2010 at 04:37:50PM -0400, soulodd wrote:
> Currently the application that is passing the X-Accel-Redirect uri back
> to nginx must set the Content-type header otherwise it will
> automatically be set to the default_type setting.
This is not true.
If not explicitly set by script together with X-Accel-Redirect -
Content-Type will be set by nginx according to extension of
redirect destination (and types/default_type defined, see ).
> Is there a way to get
> nginx to automatically detect the mime settings and transmit it?
See above for extension-based detection - this is how it works by
default. Just not returning Content-Type with X-Accel-Redirect is
If you are talking about content sniffing - no, it's not available
> tried: fastcgi_ignore_headers Content-Type, but that gave me the error
> (taken from
> [warn] 3988#1288: invalid value "Content-Type"
Directive fastcgi_ignore_headers never accepted "Content-Type"
More information about the nginx