From: Zed Shaw <zedshaw@...>
Date: 2006-02-19T06:56:31+09:00
Subject: Re: Mongrel 0.3.5 -- Rails/CGI Actually Works

Ah yes, very clever stuff going on here in CGI land.  Take a look at this
dump of what is passed to the "head" method.

>>>>
head: {}
options: {"Status"=>"200 OK", "type"=>"text/xml", "cookie"=>[],
"Cache-Control"=>"no-cache", "X-Zed"=>"dabomb"}
<<<<
>>>>
head: {"Status"=>"200 OK", "cookie"=>[], "Cache-Control"=>"no-cache",
"Server"=>"Mongrel 0.3.5", "Content-Type"=>"text/xml", "X-Zed"=>"dabomb"}
options: "text/html"
<<<<

It's basically a problem with both the head() and out() methods defaulting
to "text/html" as their content type so it gets reset when the output is
sent on.  If you change 629 of mongrel.rb to be:

        @head['Content-Type'] = options unless @head['Content-Type']

Then that will fix it.  This also means that it will default to the first
content-type set.  I'll pack that up into a fix for a release tomorrow or
later tonight.  Let me know if that works.

Proxy stuff coming soon.

Zed A. Shaw
http://www.zedshaw.com/

On 2/18/06 4:28 PM, "_blackdog" <rmt512@gmail.com> wrote:

> hi Zed
> Sorry to be the bearer of bad news.
> 
> The proxy issue is still ocurring, as is the "Wrong Content-type:"
> error returned when using webservices (xmlrpc) with 0.3.5
> 
> FYI, I tried the web service request from a webrick and mongrel server
> and they both interpreted the Wrong Content-type, so the problem is not
> in the parsing of requests but the creation of responses, but maybe
> that is totally obvious :)
> 
> thanks for your efforts
> 
> BD
> 
>