Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

CFApplication update is destroying session variables when called occasionally.

Description

When running the code in the linked repo with cookies disabled on the client you will see that the trackingId session variable is occasionally lost after calling application action='update' This is causing random errors in our legacy code that is supposed to operate on default session variables when it is a bot or a proxied request from another instance. It seems to affect all versions of Lucee. It is important when testing that the sessions are stored in Redis and that you have cookies disabled on the client so that it generates a new session on every request.

https://github.com/Yamaha32088/LuceeClusteredSessionError

I have linked another issue that is very similar to this one. There is also this issue that has already been fixed but the issue I describe above still persists.

Environment

None

Activity

Show:

Zac Spitzer 12 June 2023 at 13:25

Zac Spitzer 14 April 2023 at 12:10

Zac Spitzer 28 February 2023 at 01:57
Edited

seems it’s only a problem in 5.3, I can’t repro in 6.0

https://github.com/lucee/Lucee/pull/1970

Zac Spitzer 28 February 2023 at 00:49

I can reproduce locally with 5.3.10.122 using curl

Brandon Brown 28 February 2023 at 00:39
Edited

In development I only run a single instance. In production we have 3 instances running. It happens in both.

Details

Assignee

Reporter

Priority

Labels

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

Created 27 February 2023 at 21:09
Updated 12 June 2023 at 13:25

Flag notifications