[squid-users] tlu.dl.delivery.mp.microsoft.com and HTTP range header
Alex Rousskov
rousskov at measurement-factory.com
Tue Nov 23 15:17:31 UTC 2021
On 11/23/21 5:09 AM, David Touzeau wrote:
> tlu.dl.delivery.mp.microsoft.com is from the app store and it encounters
> an issue with high bandwidth usage.
> We think that it was caused because Squid filtering the HTTP Range
> header from the HTTP requests.
Does Squid actually filter the HTTP Range header when forwarding HTTP
requests sent by that app?
If the resource is served over a TLS connection, does your Squid bump
the corresponding transaction using the SslBump feature?
Do you disable all caching? Caching of these specific responses?
> This caused the app store download everything in an endless loop
Does Squid return a partial response to the application? It should do
that in most cases, even if it filters the HTTP Range header out when
forwarding the request to the origin server, but there are exceptions to
that general principle.
> We know that Squid is not currently compatible with http range :
> https://wiki.squid-cache.org/Features/HTTP11#Range_Requests
That wiki page does not say that Squid is incompatible with HTTP Range
feature. It says that Squid does not support caching of partial responses.
> Is there any workaround in order to avoid high bandwidth usage of
> Microsoft clients without needing caching objects ?
More information may help troubleshoot this problem. Please use the
questions above as starting points.
Thank you,
Alex.
More information about the squid-users
mailing list