Skip to content

[WIP][POC] Add custom xkeys to response - #25

Draft
adriendupuis wants to merge 1 commit into
developfrom
feature/custom-xkey
Draft

[WIP][POC] Add custom xkeys to response#25
adriendupuis wants to merge 1 commit into
developfrom
feature/custom-xkey

Conversation

@adriendupuis

@adriendupuis adriendupuis commented Apr 15, 2020

Copy link
Copy Markdown
Owner
  • Can a custom xkey be added to the default ones?
  • X-Location-Id header is deprecated; what happens when is still used?

curl -sI http://localhost:8000/ | grep xkey;
docker-compose restart varnish;
curl -sI http://localhost:8080/ | grep xkey;

Custom xkeys are added first:
xkey: l123 l456 ez-all c52 ct42 l2 pl1 p1 p2

$locationIds = [123, 456];
//$response->headers->set('X-Location-Id', implode(',', $locationIds));
$response->headers->set('xkey', 'l'.implode(' l', $locationIds));

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In eZ Platform 3, it seems to be $response->headers->set('X-Cache-Tags',...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant