Welcome! Log In Create A New Profile

Advanced

Re: Issues with default_type

James G
April 13, 2010 01:46PM
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.

~ James


Lasgo Chrysalis Limited. Registered in England & Wales No. 1380166.
Part of the Chrysalis Plc.
Registered office: The Chrysalis Building, Bramley Road, London W10 6SP


_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
Subject Author Posted

Issues with default_type

James G April 13, 2010 09:30AM

Re: Issues with default_type

Maxim Dounin April 13, 2010 12:34PM

Re: Issues with default_type

James G April 13, 2010 01:46PM

Re: Issues with default_type

Alejandro Mery April 13, 2010 04:00PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 269
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready