tracker issue : CF-3040459

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 80798:onRequestEnd() doesn't fire when <cfabort> or <cflocation> is used(I'm also 99% sure that it doesn't fire when using <cfcontent> either)It would be useful if it did

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Mark Mandel / Mark Mandel (mark.mandel)

Created: 11/25/2009

Components: Core Runtime, Application

Versions: 9.0

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 / 263146

Priority/Frequency: Normal / Unknown

Locale/System: English / Platforms All

Vote Count: 2

Problem:

onRequestEnd() doesn't fire when <cfabort> or <cflocation> is used(I'm also 99% sure that it doesn't fire when using <cfcontent> either)It would be useful if it did.
Method:


Result:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3040459

External Customer Info:
External Company:  
External Customer Name: Mark Mandel
External Customer Email: 3EA9517D445A9E8999201549
External Test Config: 11/25/2009

Attachments:

Comments:

I know this is closed (and implemented, it seems. Unfortunately). But I'd like to give a -1 to this: it's a dumb idea. Both tags are supposed to abort processing. So that's what they should do. I *could* however see an argument for adding optional params to each of these to allow for a "graceful" exit to the request, which then also runs onRequestEnd(). But it should be an option, not a unilateral change which breaks backwards compat. Suggest this is reverted in the next patch / release. -- Adam
Vote by External U.
22507 | November 11, 2011 12:38:41 AM GMT
Makes page lifecycle impossible to manage in CF code. Also inconsistent with the behaviour of onRequestStart(), which does fire after a cflocation.
Vote by External U.
22508 | November 11, 2011 12:38:42 AM GMT