Skip to content
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.

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

Incompatible with IntegerNet_SansecWatch #6

Open
norgeindian opened this issue Feb 7, 2025 · 3 comments
Open

Incompatible with IntegerNet_SansecWatch #6

norgeindian opened this issue Feb 7, 2025 · 3 comments
Assignees

Comments

@norgeindian
Copy link

norgeindian commented Feb 7, 2025

We were just facing a strange issue.
We switched from manually including a CSP whitelist to the module IntegerNet_SansecWatch, which dynamically updates the headers based on the given settings in the Sansec panel.
It seems, that both modules are not compatible.
At least, we got the error: Unable to set the CSP header. The header size of 8211 bytes exceeds the maximum size of 8190 bytes.
We had the exact same CSP whitelist included before in a module, and there it worked.

@norgeindian
Copy link
Author

Debugged that further, and it seems, that it was only a caching issue.
At least it seems to work as expected, when I debug it locally.

@norgeindian
Copy link
Author

No, sorry, have to open it again :-)
Was not able to reproduce the issue locally, but on our testing system it can directly be reproduced.
As soon as I activate in Sansec too many policies, so that the header is too big, and update the policies, apache directly gives up.
The question now is, on which side would we need to trigger something to fix it.
IntegerNet_SansecWatch flushes or invalidates the FPC.
I tried both, but that does not fix it.
Does anyone have an idea, what I could try to fix this issue?

@norgeindian norgeindian reopened this Feb 11, 2025
@lsiebels
Copy link
Collaborator

Hi @norgeindian, thanks for reporting the problem.

It seems to me that the problem is related to the issue #5. Please try to lower the threshold as described in the issue.

@lsiebels lsiebels self-assigned this Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants