>>! In T196558#4261915, @Krinkle wrote:
> I'll re-open this for a slightly different purpose, which is to find a way to avoid sending X-Analytics as data to the end user from Varnish. Instead, we can explore other options to communicate between Varnish VCL and the consumer of this field (which is varnishkafka > webrequests table in Hive/Hadoop).
> That was actually the reason I pinged @mforns earlier today when this task was filed.
>>>!Currently X-Analytics data is passed from Varnish to Hadoop via HTTP headers. In T194814#4262008Those headers are then passed to clients, @Vgutierrez wrote:
>> @ema Could we use std.log (VCL_Log) to report X-Analytics data and stop the header from reaching the final user?which sends pointless data to end users.
Instead of relying on headers, this data could be passed by Varnish via VCL_Log, which lets it pass data to the backend without exposing headers to the client.
This would reduce our outbound bandwidth and the amount of useless data in the first TCP packet the client received, leaving more room for actual content actionable by the web browser.