Re: possible bug in Mason 1.36

>Specifically, why would setting $r->content_type to '' instead of
>undef be the trigger? Mason's (potentially broken) code to determine
>whether headers were sent should work the same way in both of those cases.

IMHO, this is definitely the crux of the issue.  Apache accepts '' as the content_type which is evident in that it comes out as '' in the http headers when Mason's out method sends the headers the first time.   However, as I pointed out in my original post, there's a check further down in the Mason code that query's Apache for the content type... Apache returns undef even though '' was sent for the content_type so Mason thinks no headers were sent and sends them again.

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

_______________________________________________
Mason-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-devel