[
https://issues.apache.org/jira/browse/WW-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564795#comment-17564795
]
Lukasz Lenart commented on WW-5203:
-----------------------------------
The question is: which one is a proper behaviour? Interceptors are _long living
instances_ and singletons (per interceptor stack), so once created they remain
unchanged during _the whole life cycle_ and in this case once the policy
builder was initialised it will remain unchanged, yet there is a unit test
which covers _chanability_ of the builder. [~saldiaz] could you help us
understand this?
> lazyPolicyBuilder in DefaultCspSettings is not lazy
> ---------------------------------------------------
>
> Key: WW-5203
> URL: https://issues.apache.org/jira/browse/WW-5203
> Project: Struts 2
> Issue Type: Bug
> Components: Core Interceptors
> Affects Versions: 6.0.0
> Reporter: Guido L. Woestmann
> Priority: Critical
> Fix For: 6.0.1
>
> Attachments: struts-ww-5203-make-lazy.patch,
> struts-ww-5203-normal-supplier.patch
>
>
> The "lazyPolicyBuilder" inside DefaultCspSettings is supposed to create the
> CSP-Policy-String only once. But the Variable "hasBeenCalled" isnt set to
> false anywhere, so the String will be created every time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
