atom feed18 messages in org.apache.tcl.rivet-dev[Bug 57501] abort_page does not stop ...
FromSent OnAttachments
bugz...@apache.orgApr 17, 2015 8:12 am 
bugz...@apache.orgApr 17, 2015 9:28 am 
bugz...@apache.orgApr 17, 2015 10:54 am 
bugz...@apache.orgApr 17, 2015 11:58 am 
bugz...@apache.orgApr 18, 2015 6:52 am 
bugz...@apache.orgApr 18, 2015 10:16 am 
bugz...@apache.orgApr 20, 2015 12:52 pm 
bugz...@apache.orgApr 21, 2015 6:48 am 
bugz...@apache.orgApr 21, 2015 11:50 pm 
bugz...@apache.orgApr 27, 2015 8:20 am 
bugz...@apache.orgApr 29, 2015 9:27 am 
bugz...@apache.orgApr 30, 2015 5:41 pm 
bugz...@apache.orgMay 4, 2015 7:27 am 
bugz...@apache.orgMay 4, 2015 9:42 am 
bugz...@apache.orgMay 4, 2015 10:12 am 
bugz...@apache.orgMay 6, 2015 7:09 am 
bugz...@apache.orgMay 10, 2015 1:16 pm 
bugz...@apache.orgMay 12, 2015 9:43 am 
Subject:[Bug 57501] abort_page does not stop page execution after a call to ::rivet::parse
From:bugz...@apache.org (bugz@apache.org)
Date:May 6, 2015 7:09:27 am
List:org.apache.tcl.rivet-dev

https://bz.apache.org/bugzilla/show_bug.cgi?id=57501

--- Comment #28 from jame@flightaware.com --- Thanks for the patch. All my tests pass, and I'm no longer seeing errors in httpd.log when calling abort_page.

abort_page, when called from within a parsed parsed, aborts the entire page, including the caller.

To make sure we're on the same page, AfterEveryScript is not called (I believe) when a parsed page finishes. My test is using abort_page as the AfterEveryScript. When I do that, if I do not call abort_page explicitly from within the parsed page, page execution continues in the caller.

I think that's reasonable behavior, although I could see the argument for calling AfterEveryScript after the parsed page, since it too is a script.