ColdFusion 9.0  -  Bug 3040459

Created on Wednesday, November 25, 2009

Login for more options

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

Description

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:

Test Configuration

11/25/2009

App Language(s) English
OS Language(s) English
Platform(s) Platforms All
Browser(s)

Notes (0)

Duplicate ID
Reported By mark.mandel

Status

State Closed
Status Fixed
Reason

Importance

Priority 2-Medium
Frequency Unknown
Failure Type Unspecified
Product Area Core Runtime

Build

Found In Build 0000
Fixed In Build 263146

Attachments (0)

No Files Attached

Votes (2)

  • jmetcher

    10:08:42 PM GMT+00:00 Nov 10, 2011

    Makes page lifecycle impossible to manage in CF code. Also inconsistent with the behaviour of onRequestStart(), which does fire after a cflocation.

  • Adam Cameron.

    10:08:41 PM GMT+00:00 Nov 10, 2011

    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

Your session has expired! Click to login
Current form data will be preserved

Cancel