Issues with default_type
Alejandro Mery
amery at geeks.cl
Tue Apr 13 23:51:33 MSD 2010
On Tue, Apr 13, 2010 at 19:39, James G <james.g at lasgo.co.uk> wrote:
>
> On 13 Apr 2010, at 17:25, Maxim Dounin wrote:
>
>> Hello!
>>
>> On Tue, Apr 13, 2010 at 02:22:41PM +0100, James G wrote:
>>
>>> Here's a snippet of my configuration:
>>> location /resource/image/
>>> {
>>> default_type image/jpeg;
>>> add_header Content-Type image/jpeg;
>>> mogilefs_tracker 192.168.0.1:7001;
>>> mogilefs_domain 'repository:images';
>>>
>>> mogilefs_pass
>>> {
>>> proxy_pass $mogilefs_path;
>>> proxy_hide_header Content-Type;
>>> proxy_buffering off;
>>> }
>>> }
>>>
>>> So I've set the default type, forced the header with add_header, and
>>> told the proxy_pass not to send the Content-Type header. So we
>>> should be getting the Content-Type of "image/jpeg", right?
>>
>> Try setting default_type in mogilefs_pass{} block, it should fix
>> your issue.
>
> Sadly, it hasn't. I'm still getting Content-Type: text/plain back. Any other
> suggestions or ideas are welcome.
I suppose you moved *both* (add_header and default_type), right?
More information about the nginx
mailing list