3.0.3

What's Changed

• BUGFIX: Adapt cache flushing to Neos 9 cache flushing by @dlubitz in #27

New Contributors

• @dlubitz made their first contribution in #27

Full Changelog: 3.0.2...3.0.3

3.0.2

What's Changed

• Declare compatibility with Neos 9 by @mficzel in #23

Full Changelog: 3.0.1...3.0.2

3.0.1 Fix cache flushing behavior

BUGFIX: Use actual tags and not log messages to flush

3.0.0

What's Changed

• TASK: Adjustments for Neos 8 by @mficzel in #18

Full Changelog: 2.1.1...3.0.0

2.1.1

Full Changelog: 2.1.0...2.1.1

2.1.0

What's Changed

• Removed duplicated key maxPublicCacheTime by @paavo in #13
• TASK: Make caching behavior opt-in via X-FullPageCache-EnableFusionAutoconfiguration http header by @mficzel in #16

New Contributors

• @paavo made their first contribution in #13

Full Changelog: 2.0.0...2.1.0

Neos 7.0 compatibility

The http components are converted to middlewares to be compatible with Flow and Neos 7.

In addition instead of checking the flow session the request is validated against cookie and parameter allow and
ignore lists that can be defined via setting

    # requests have to fulfill certain conditions for beeing cached
    request:
      # !!! Only the http methods "GET" and "HEAD" are supported !!!

      # a request will only qualify for caching if it contains no cookieParams that
      # are not ignored.
      cookieParams:
        # ignored cookie params exclude cookies that are handled by the frontenecn
        # and are not relevant for the backend. A usecase would be gdpr consent cookies
        # if they are only used on the client side
        ignore: []

      # a request will only qualify for caching if it only contains queryParams that
      # are allowed or ignored. All other arguments will prevent caching.
      queryParams:
        # allowed params become part of the cache identifier, use this for
        # arguments that modify the reponse but still allow caching like pagination
        allow: []

        # ignored arguments are not part of the cache identifier but do not
        # prevent caching either. Use this for arguments that are meaningless for
        # the backend like utm_campaign
        ignore: []

The creation of the 304 state is removed as the standardsCompliance middleware handles this already.
Obviously the version requirement had to be raised.

Resolves #12

1.0.2

Merge pull request #5 from Flowpack/bugfix/error-with-single-cachetag

BUGFIX: Prevent error with single cache tag

Security Bugfix

1.0.1

BUGFIX: Reponses with `Set-Cookie` should never be cached

Initial Release

This package will still do quick iterations, be prepared for major version releases with breaking changes soon, so do your requires accordingly.