Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've created a tool on our intranet where a user can send a (big) tgz file using a simple/basic html form (POST/multipart).

When using either firefox or IE:

  • The form is not sent when the file is too large (2.44 Go)
  • It succeeds when the file is smaller.
  • It fails for the large file with for some other forms found on the web and having a "Select File..." input.
  • (update) Sending the same big file on another computer works fine.

So, is there restriction parameter in XP fixing a maximum size for this kind of POST query ?

Many thanks,


share|improve this question

I believe that the limit isn't in the client, but is rather on the server.

For example, for IIS7 I usually use the following command to extend the limit to 100000000 bytes:

%windir%\system32\inetsrv\appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:100000000

The server must also be capable of handing such large files. An easy mistake is to keep the file in memory, thus exceeding the capabilities of a server with only 4GB of RAM.

share|improve this answer
It's a client problem. Sending the same file on another computer works fine. – Pierre Aug 30 '10 at 13:42
@Pierre: If the browser is the same on both machines, there is no reason that it will malfunction on XP. XP itself has no mechanism for limiting socket traffic. It might be that a parameter of the browser limits the time that it is willing to wait, or that a badly parametered antivirus decided to intervene. – harrymc Aug 30 '10 at 13:52
@Pierre: Idea - Is there a difference between the machines as regarding 32-bits / 64-bits ? – harrymc Aug 30 '10 at 13:54
@harrymc thanks. The computer that failed is a 64 bits OS, the other machines are 32 bits. – Pierre Aug 30 '10 at 14:09
@Pierre: Do you mean that it works on 32-bits and fails on 64-bits? I would have thought just the opposite. – harrymc Aug 30 '10 at 15:31

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .