Skip to content

Set fixed version on link to http-cache config #2747

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
May 19, 2025
Merged

Set fixed version on link to http-cache config #2747

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/infrastructure_and_maintenance/cache/http_cache/reverse_proxy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Using a different proxy is highly recommended as they provide better performance

For reverse proxies to work properly with your installation, you need to add the corresponding VCL files for your HTTP Cache.

- [Varnish VCL xkey example](https://github.com/ibexa/http-cache/blob/main/docs/varnish/vcl/varnish5.vcl)
- [Varnish VCL xkey example](https://github.com/ibexa/http-cache/blob/4.6/docs/varnish/vcl/varnish5.vcl)
- Fastly can be found in `vendor/ibexa/fastly/fastly`. You must install the following to use Fastly:
- `ez_main.vcl` as the **main** custom VCL
- `ez_user_hash.vcl` as another custom VCL
Expand Down Expand Up @@ -155,7 +155,7 @@ If you want to use Basic Auth with Fastly on [[= product_name_cloud =]], please

!!! note "Invalidating Varnish cache by using tokens"

In setups where the Varnish server IP can change (for example, on [[= product_name_cloud =]]), you can use token-based cache invalidation through [`ez_purge_acl`](https://github.com/ibexa/http-cache/blob/main/docs/varnish/vcl/varnish5.vcl#L174).
In setups where the Varnish server IP can change (for example, on [[= product_name_cloud =]]), you can use token-based cache invalidation through [`ez_purge_acl`](https://github.com/ibexa/http-cache/blob/4.6/docs/varnish/vcl/varnish5.vcl#L174).

In such situation, use strong, secure hash and make sure to keep the token secret.

Expand Down