Re: possible bug in Mason 1.36

On Fri, 24 Aug 2007, Scott Lanning wrote:

> On Fri, 24 Aug 2007, Scott Lanning wrote:
> [...]
>> That is, the Content-type is undef, and no additional
>> set of headers is output. Q.E.D. :)
>
> On second thought... it's only half the story, I guess,
> because the Content-type should be 'text/html; charset=utf-8'
> not undef. It's still true that extra headers aren't sent
> when Content-type is set to undef.

Well, like I said, if you set the Content-type header before passing 
control to Mason, _and_ the request is for a directory, I would expect 
that Content-type setting to get erased.

I think this can all be improved by having Mason simply use $r->notes to 
track whether or not it has sent headers.


-dave

/*===================================================
VegGuide.Org                        www.BookIRead.com
Your guide to all that's veg.       My book blog
===================================================*/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/