On Wed, 2010-03-10 at 14:18 +0100, Peter Pöml wrote:
They use a product called Ironport[1] that intercepts requests to the Internet, and interferes with them. It is like "forced" proxy, so to speak.
This is typically referred to as a "transparent" proxy.
1) Is Ironport's interception broken, in that it changes the passed headers to something invalid? 2) Is aria2c not correctly dealing with servers that ignore byte ranges I guess that 1) is the case, because if Ironport removes byte range headers from the client, it clearly should also remove the server's announcement for support of byte ranges (which practically all mirrors announce): the "Accept-Ranges: bytes" header. So IMO what we see is a violation of RFC2616 by the Ironport appliance. Might be worthwhile to open a bug with its manufacturer.
--
Adam Tauno Williams