Skip to content

Mark CBCsrf as threadSafe to avoid handing out a half-wired singleton #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lmajano merged 1 commit into from
Sep 10, 2026
Merged

Mark CBCsrf as threadSafe to avoid handing out a half-wired singleton #16

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Fixed

- Marked `CBCsrf` as `threadSafe` so WireBox publishes the singleton only after
autowiring it. Concurrent requests hitting a cold singleton cache (right after a
framework reinit, for instance) could otherwise get a half-wired instance and fail
with `variable [CACHESTORAGE] doesn't exist`.

## [3.2.0] - 2025-02-19

### Added
Expand Down
2 changes: 1 addition & 1 deletion models/cbcsrf.cfc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
* ---
* Service that encapsulates token security against cross site request forgery (csrf)
*/
component accessors="true" singleton {
component accessors="true" singleton threadSafe {

/* *********************************************************************
** DI
Expand Down
Loading