Jochen Wiedmann wrote: > On 9/12/07, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote: > >> But within IE7, the request is truncated at 4864kb instead of the >> expected 6mb. My best guess is that IE believes it can grok the file >> as it's advertised content type. > > Is it possible that the browser invokes a content handler (for example > winzip or something like that) on the transferred file, which detects > at some point, that the mime type is wrong and therefore fails, > causing the browser to abort the connection?
This is pretty much a virgin 2003 R2 SP2 Server with Visual Studio 2005 installed, upgraded to IE7. It really isn't that decorated, a quick delve shows that HKCR/.tar does map to Content Type application/x-tar (as it should) and that's associated to PercievedType compressed. Simply the windows compressed folder handler. Yet and still, this was a save as file, not an attempt to open. FWIW MS maps .tgz to Content Type application/x-compressed, whatever the heck that's supposed to mean :) Bill
