Details
-
Bug
-
Resolution: Won't Fix
-
High
-
5.4.9, 1.8.1
-
None
-
Sprint 6
Description
It's possible to use the anonymous_user_id to set different anonymous users for different siteaccesses so each siteaccess will have a different set of permissions for the anonymous users.
To see how this is configured:
$ app/console config:dump-reference ezpublish --env=dev
ezpublish:
system:
siteaccess_name:
# The ID of the user used for everyone who is not logged in.
anonymous_user_id: ~ # Example: 10
eZ Publish has a varnish.vcl file where you can set the X-User-Hash thta will be used to detect and handle anonymous users cache:
if (req.http.Cookie !~ "eZSESSID" && !req.http.authorization) { set req.http.X-User-Hash = "38015b703d82206ebc01d17a39c727e5"; }
Now, if you use anonymous_user_id to configure multiple anonymous users, how the X-User-Hash should be configured so Varnish will work nicely?
It's important to document this.
Attachments
Issue Links
- relates to
-
EZP-26379 Documentation: Update information on Varnish user hash
- Closed