Re: [Mason] Problem upgrading from 1.28; headers flushed too soon on $m->redirect()?

[Michael Burns]

Howdy all, Following up to my previous post, the problem seems to be exclusively with $m->clear_buffer() and component-with-content calls. The behaviour has changed between Mason 1.28 and 1.29_01. If you have a "test.html" component that contains the simple: - - - - - - - - - - Shouldn't see this... <&| .Foo &> <& .Bar &> </&> <%def .Foo><% $m->content %></%def> <%def .Bar> % $m->clear_buffer; </%def> - - - - - - - - - - Under Mason 1.28, the raw server response is the expected: - - - - - - - - - - HTTP/1.1 200 OK Date: Sat, 21 Jan 2006 03:15:41 GMT Server: Apache/1.3.34 Connection: close Transfer-Encoding: chunked Content-Type: text/html - - - - - - - - - - However under Mason 1.29_01, the buffer isn't actually cleared ... this is the raw server response: - - - - - - - - - - HTTP/1.1 200 OK Date: Sat, 21 Jan 2006 03:22:21 GMT Server: Apache/1.3.34 Connection: close Transfer-Encoding: chunked Content-Type: text/html Shouldn't see this... - - - - - - - - - - Something to do with component stack handling changes in 1.29_01 and $m->clear_buffer() not bubbling up/clearing things properly? For reference, if you don't have the nested component, it seems to work fine. This variation outputs the expected empty response on both Mason 1.28 and Mason 1.29_01: - - - - - - - - - - Shouldn't see this... <&| .Foo &> % $m->clear_buffer; </&> <%def .Foo><% $m->content %></%def> - - - - - - - - - - -Michael _______________________________________________________ Michael Burns Cosbit Technologies 403-701-2672  / [EMAIL PROTECTED] AIM: cmikeburns MSN: cmikeburns _______________________________________________________ Box 2173, Station M  •  Calgary, Alberta, Canada  •  T2P 2M4 http://cosbit.com