Re: possible bug in Mason 1.36

On Mon, 20 Aug 2007, David E. Wheeler wrote:

> On Aug 20, 2007, at 07:55, Dave Rolsky wrote:
>
>> Hmm, this is weird. I don't see how this would've worked before, since
>> Mason would've overridden the content type when the request was for a
>> directory. And I definitely don't see why this would break after
>> upgrading
>> Mason to 1.36, since that hasn't fundamentally changed.
>
> So how can we globally set it again?

Globally set the content type, you mean?

My point was simply that while I don't understand how this code worked 
with Mason 1.35, there's no reason it shouldn't continue to work with 1.36 
;)


-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/