Issues

Select view

Select search mode

 

Log trace of cflocation and allow option to Abort

Fixed

Description

Applications that use cflocation heavily are difficult to debug. This enhancement will log a stack trace to the trace log and add the boolean attribute abort=[false] which when set to true, will throw an error instead of returning the cflocation header.

Attachments

1

Details

Assignee

Reporter

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Priority

Created 23 September 2021 at 22:28
Updated 4 January 2023 at 18:44
Resolved 24 September 2021 at 15:04

Activity

Show:

Brad Wood4 January 2023 at 18:44

Good to know. Is that why I also couldn’t get the logging to show up in the trace log in Lucee 5.3.9?

Zac Spitzer4 January 2023 at 08:48

good catch, seems it was added to the 5.3.8 branch, not 5.3

5.3 (aka 5.3.10)

5.4

Brad Wood3 January 2023 at 22:17
Edited

I don’t see the abort attribute for cflocation in the docs:

https://docs.lucee.org/reference/tags/location.html

Zac Spitzer16 November 2022 at 09:23

avoid a callstackget unless required

Zac Spitzer24 September 2021 at 15:01
Edited

by default, the trace log is set to ERROR, if set to INFO, you now see the following style of entries

"INFO","http-nio-8888-exec-8","09/24/2021","16:57:20","cftrace","redirect to server.cfm?action=server.logging at /admin/server.logging.create.cfm:79; /admin/server.logging.cfm:66; /admin/web.cfm:492; /admin/server.cfm:2"

with abort=true, an exception is thrown like this

Flag notifications