Say i vary on the X-User header, but start looking into cookies from cookie that varnish is not putting into the X header. Single tests work fine, but overlapping requests can collide. Or get confused, if i add another cookie to track some state. Then again, this is not a design decision, just a doc question. The user of the lib can still choose.

Other opinions on this?

----- Reply message -----
Von: "Joel Wurtz" <notifications@github.com>
An: "FriendsOfSymfony/FOSHttpCache" <FOSHttpCache@noreply.github.com>
Cc: "David Buchmann" <david@liip.ch>
Betreff: [FOSHttpCache] Add tests for head request, and add cookies on a hit for pass action (#62)
Datum: Fr., Mai. 23, 2014 18:41
In doc/varnish-configuration.md:
>  ```
>  
>  If your application’s user authentication is based on cookie other than
>  PHPSESSID, change `PHPSESSID` to your cookie name.
>  
> +We also need to change the Vary header in the HEAD response.
> +
> +```php
> +header('Vary: X-User-Id');

Or we just tell the two solution and let's user decide what he wants ?

For me, i prefer to extract as i find it more robust and painless. 

I see also your point as you maybe do not want to change backend in the same time as you change the varnish (need to do a sync migration)


i maybe won't notice that i start mixing up the hash between different groups


I'm certainly misunderstanding, but i don't see how this can happen ?

&mdash;
Reply to this email directly or view it on GitHub.