HTTP Error: 413 Request entry too large

  • Simon
    6th Feb 2011 Administrator 0 Permalink
    I'll increase the Max upload size a little.
    Edit: The max upload limit on the server is 20 MB, this must be a hardcoded limit in the client.
  • Mur
    6th Feb 2011 Member 0 Permalink
    @MasterMind555
    You never heard of dial-up internet connection? Its max speed is 56kbps, and the normal speed is between 10kbps and 40kbps...
  • Hellome
    6th Feb 2011 Member 0 Permalink
    {QuietVoice}

    >but what format are saves............

    {/QuietVoice}
  • JoJoBond
    6th Feb 2011 Member 0 Permalink
    @Simon
    https://github.com/FacialTurd/The-Powder-Toy/blob/master/src/interface.c#L3562
    So It sends 6 things to the server:
    - Name: Unproblematic
    - Description: Unproblematic
    - Data: The save (basically a stamp file) Shouldn't be the problem.
    - Thumbnail: If it's BMP info then the max size would be 688 KByte. So this shouldn't be the problem.
    - Publish: Unproblematic
    - ID: Unproblematic
    There is no hard coded limit to be found. (The 413 comes from the server).

  • JoJoBond
    6th Feb 2011 Member 0 Permalink
    Sorry for double post, but I still encounter the problem therefore I made a packet trace to check the file sizes, which are OK. The whole log is < 1MB with all the info in it which is actually sent to the server so I can surely say it's a server problem.
    http://pastebin.com/F8HY1c4W
  • Simon
    6th Feb 2011 Administrator 0 Permalink
    Okay, I found the issue, there was a limit in another piece of software at 1MB, it has been increased to 4MB, please confirm the issue has been fixed.
  • cracker64
    6th Feb 2011 Developer 0 Permalink
    a full screen of dust and messing with heat/cool still does not publish.
  • JoJoBond
    6th Feb 2011 Member 0 Permalink

    cracker64:

    a full screen of dust and messing with heat/cool still does not publish.

    I can confirm that.
  • Simon
    6th Feb 2011 Administrator 0 Permalink
    Okay, after a bit more debugging, it seems the issue is not a configuration issue, it's with the http server, I'm trying to find a solution