26 Aug
2010
26 Aug
'10
19:42
On Thu, Aug 26, 2010 at 09:27:53PM +0200, Josef Wolf wrote:
Turns out, that a broken proxy was the problem. The proxy delivered a Content-Length header of about 51 MB. So the client has never had a chance to do a correct download. Guess the proxy had problems with the 4GB limit.
Unfortunately, there are still quite some proxies out there which can't handle large files. Thanks for posting the result of your quest.
With a wrong Content-Length header, all chances are gone, IMHO.
...and the Content-Range header would probably show the same irregularities.
But what do you do if your only access is HTTP via proxy?
I can't think of anything else productive right now than pointing out the problem to the folks who operate the intermediary proxy. Peter