aoe / varnish
Enable varnish support with tags
12.1.1
2026-03-05 13:54 UTC
Requires
- php: ^8.0
- guzzlehttp/guzzle: ^7.2
- typo3/cms-backend: ^11.5 || ^12.4
- typo3/cms-core: ^11.5 || ^12.4
- typo3/cms-extbase: ^11.5 || ^12.4
- typo3/cms-frontend: ^11.5 || ^12.4
Requires (Dev)
- phpcompatibility/php-compatibility: ^9.3
- phpstan/phpstan: ^2.1
- rector/rector: ^2.0
- symplify/easy-coding-standard: ^12.0
- symplify/phpstan-rules: ^14.6
- typo3/testing-framework: ^7.0 || ^8.0
Conflicts
- 12.1.1
- 12.1.0
- 12.0.3
- 12.0.2
- 12.0.1
- 12.0.0
- 11.1.1
- 11.1.0
- 11.0.7
- 11.0.6
- 11.0.5
- 11.0.3
- 11.0.2
- 11.0.1
- 11.0.0
- dev-main / 10.x-dev
- 10.1.2
- 10.1.1
- 10.1.0
- 10.0.4
- 10.0.3
- 10.0.2
- 10.0.1
- 10.0.0
- 7.2.0.1
- 7.2.0.0
- 1.4.5
- 1.4.4
- 1.4.3
- 1.4.2
- 1.4.1
- 1.4.0
- 1.3.1
- 1.3.0
- dev-master / 1.2.0.x-dev
- 1.2.0
- 1.1.0
- 1.0.1
- 1.0.0
- 0.6.4
- 0.6.3
- 0.6.2
- 0.6.1
- 0.6.0
- 0.5.0
- 0.4.4
- 0.4.3
- 0.4.2
- 0.4.1
- 0.4.0
- 0.3.0
- 0.2.1
- 0.2.0
- 0.1.0
- 0.0.3
- 0.0.2
- 0.0.1
- dev-TYPO3_12
- dev-feature/codestyle_migration
- dev-TYPO3V11
- dev-TYPO3V8
- dev-TYPO3V7
This package is auto-updated.
Last update: 2026-03-05 13:57:03 UTC
README
This is a TYPO3-Extension that integrates the popular Varnish HTTP Cache into TYPO3.
Download / Installation
You can download and install this extension or use composer.
Copyright / License
Copyright: (c) 2016 - 2024, AOE GmbH License: GPLv3, http://www.gnu.org/licenses/gpl-3.0.en.html
Documentation
The documentation is available online at [docs.typo3.org][2].
If you want you can also render the documentation locally, this can be really helpful when adjusting the documentation to check before commiting.
The local rendering requires docker and can be done like this:
docker run --rm --pull always -v $(pwd):/project -it ghcr.io/typo3-documentation/render-guides:latest --config=Documentation
And then open Documentation-GENERATED-temp/Index.html with your browser.
Contributing
1. Fork the repository on Github
2. Create a named feature / bugfix branch (like `feature_add_something_new` or `bugfix\thing_which_does_not_work`)
3. Write your change
4. Write tests for your change (if applicable)
5. Run the tests, ensuring they all pass
6. Submit a Pull Request using Github