-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/07/2015 02:30 PM, Rubén Romero wrote: > > While on the topic of changing defaults, I think we should include > Surrogate-Control and ESI parsing in to the builtin VCL as > discussed yesterday. > > This was discussed last year: > https://www.varnish-cache.org/trac/wiki/VDD14Q3#Surrogate-Control > > So we now need to follow-up on that and the discussions during VUGX > last week.
The conversations we've had in the past were more about using Surrogate-Control to set TTLs that are targeted to the proxy, but not for downstream caches. I believe we never got further than "yes we should have that, and a VMOD should do it" -- partially my fault, I should add in fairness. I didn't want to get nitpicky about this at VUG, but there's a bit of a problem with Varnish adding Surrogate-Control:ESI/1.0 to the backend request header (whether by default or not), since Varnish does not in fact support the full 1.0 ESI spec -- only the include and remove tags. If the idea is that backends are informed that they can use ESI in their responses, either for Varnish or, say, a CDN that might use another proxy, "ESI/1.0" would suggest that the backends can use ESI tags that Varnish would ignore. If we really want to do this, the tag might have to be something like "ESI/Varnish" or "ESI/include&remove" or "VESI/x.y". (There's a precedent for the latter -- Oracle Web Cache uses "ORAESI/x.y.z".) Of course, by the time we get to 5.0, fetch processors might be far enough along that the full ESI spec could be supported (but if so, I suspect that it will be left to a VMOD, which of course could also take care of generating Surrogate-Control headers). Best, Geoff - -- ** * * UPLEX - Nils Goroll Systemoptimierung Scheffelstraße 32 22301 Hamburg Tel +49 40 2880 5731 Mob +49 176 636 90917 Fax +49 40 42949753 http://uplex.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWZZIZAAoJEOUwvh9pJNURZr4P/0ylF3moKWHaDPD89vY/7dDp 8kKFXs2lqO2z3HD3sqMWn2JejvTbG3abef/0BwKcPnv9LN0ycSe/yYOOWB/FaeIw hJ4XprMJXJcTfGEg6RaJW5EjytGA2+kFNkUm173ms4Y6Z2LA1T9fXLLC3N6clzAm 37oGPCxo2Gud8dLITOVWsCvav0Xk1q9oa+ah6ZKESKgj9w29im5uY6XuIFksbLdG Y5TZTsk17BWSLFAiXFqNxpQFyRw/YHHR+y/nlE2wsrYj7B3mXX4nlVLnGzB6dGsA nZ3XwWohTGia7s+UEKXCEI/eCBlm0wyWyzLgvzuHph4NzM7pVYHSs77Dz2EVZLd9 yWRV0D2ffnKlicHaWBznMhrNMV1igtF+gWSfaFwfLzFd/lusaEfY2CNMgO/0KZn6 sdJ9YWRtLjYAEIOc+5B3NACbSPSvj8SDlS+a4bBm01eZ6DK1rdgQMehOL46Wqq/1 A+qznlnVSL+DAWlS5Wlb8fyWV78+QZ4XK/Y4FVmWm7AxgoL6kXzv7bvNo4oQgyXU s/2iVjld/buE4WgpmNNWA2O7IdeQYUXOFhBgre/nMpHU2UHJtyz3H6pkKKaV6EGo 6b/6v0/SMn+5h/1ORk/3fX2cdo681m9+y7Kf9ne8PwGJwVCsBsnNLTCjUwdAXZPT 4ebwFjPAdNXswSkq327m =sAc4 -----END PGP SIGNATURE----- _______________________________________________ varnish-dev mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
