Boost Cacheability Settings seems not to work properly

Created on 3 December 2022, almost 2 years ago
Updated 20 April 2024, 7 months ago

Problem/Motivation

I tried to exclude specific aliases and <front> via config but the page request was cached.

Steps to reproduce

Just do the same as described above,

Proposed resolution

Fix and improve form information-

Remaining tasks

-

User interface changes

Better help texts.

API changes

-

Data model changes

-

🐛 Bug report
Status

Active

Version

1.0

Component

Caching logic

Created by

🇩🇪Germany c-logemann Frankfurt/M, Germany

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇬🇧United Kingdom kevster

    D 9.5.10
    boost 8.x-1.x-dev

    Im having the same problem - Im tyring to exclude the contact pages but no matter what settings I try in the Boost Path Cacheability Settings it is still caching form data?

    I have 3 page URLs added to hide but its caching these and not caching any other pages now so doing the opposite of what is needed?

  • 🇬🇧United Kingdom kevster

    Because we were seeing webforms displaying the latest previous submission this is a privacy/data issue. I had no option but to uninstall the boost module. As soon as I deleted the webform page from the boost cache the issue disappeared - I tried to set the form fields as autocomplete=off and same with form but this didnt help.

    Until the "Boost Path Cacheability Settings" works so certain paths/pages can be excluded I cant use this module. Exposing submitted form data in my eyes is a pretty big issue.

    I hope this can be sorted as its a great module.

  • 🇬🇧United Kingdom kevster

    setting to major as this exposes a privacy issue on webforms

  • 🇩🇪Germany c-logemann Frankfurt/M, Germany

    Because the core logic to display blocks is based on regex this will not be the suggested method in future. Maybe there will be an API/UI change to get this working.
    But there will be an additional method for excluding/including logic I currently also develop for the firewall module . A partial paths would be possible ('/some/path/*'). But I also have ideas to check paths like "/dynamic/*/something" faster as core is currently doing with regex.

Production build 0.71.5 2024