Request Entity Too Large

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Paulitos
    New Member
    • Apr 2012
    • 11
    • 4.1.x

    [Forum] Request Entity Too Large

    Request Entity Too Large

    The requested resource
    /newattachment.php
    does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.
    Good morning,
    we changed the server.
    When I upload a photo in my album I get the error indicated.
    I proceeded to set different values ​​for labum annexes, but when I load a photo in my album takes forever vBulletin parameters specified for attachments
    Thank you





    Last edited by Paulitos; Sat 24 Nov '12, 11:46am.
  • Trevor Hannant
    vBulletin Support
    • Aug 2002
    • 24325
    • 5.7.X

    #2
    On your AdminCP Home page, what are the following values:

    PHP Max Post Size
    PHP Memory Limit
    MySQL Packet Size
    Vote for:

    - Admin Settable Paid Subscription Reminder Timeframe (vB6)
    - Add Admin ability to auto-subscribe users to specific channel(s) (vB6)

    Comment

    • Paulitos
      New Member
      • Apr 2012
      • 11
      • 4.1.x

      #3
      Originally posted by Trevor Hannant
      On your AdminCP Home page, what are the following values:

      PHP Max Post Size
      PHP Memory Limit
      MySQL Packet Size


      - - - Updated - - -

      update:
      in the same server there is another forum that has no problems with vbulletin
      In the copy from the old server to the new forum could be gone permission on some files that vbulletin law to set the image size ..?
      Hello
      thanks

      Comment

      • Trevor Hannant
        vBulletin Support
        • Aug 2002
        • 24325
        • 5.7.X

        #4
        Is there anything in your server error logs for the time of the errors?
        Vote for:

        - Admin Settable Paid Subscription Reminder Timeframe (vB6)
        - Add Admin ability to auto-subscribe users to specific channel(s) (vB6)

        Comment

        • George L
          Former vBulletin Support
          • May 2000
          • 32996
          • 3.8.x

          #5
          Are you using Varnish cache ? Varnish cache 3.0.2 renamed HTTP 400 Bad Request errors to HTTP 413 Request Entity Too Large http://vbtechsupport.com/2084/.

          If you have Varnish cache you need to contact your web host or who ever setup and configured Varnish cache for you to fix the problem which is also outlined at http://vbtechsupport.com/1773/

          HTTP 400 Bad Request errors which occur when http_resp_hdr_len and http_req_hdr_len are set too low, are now renamed to HTTP 413 Request entity too large.
          :: Always Back Up Forum Database + Attachments BEFORE upgrading !
          :: Nginx SPDY SSL - World Flags Demo [video results]
          :: vBulletin hacked forums: Clean Up Guide for VPS/Dedicated hosting users [ vbulletin.com blog summary ]

          Comment

          • Paulitos
            New Member
            • Apr 2012
            • 11
            • 4.1.x

            #6
            Originally posted by Trevor Hannant
            Is there anything in your server error logs for the time of the errors?
            Originally posted by George L
            Are you using Varnish cache ? Varnish cache 3.0.2 renamed HTTP 400 Bad Request errors to HTTP 413 Request Entity Too Large http://vbtechsupport.com/2084/.

            If you have Varnish cache you need to contact your web host or who ever setup and configured Varnish cache for you to fix the problem which is also outlined at http://vbtechsupport.com/1773/

            Thank you, but in the server there is another forum that has no problems with vbulletin...

            Comment

            • George L
              Former vBulletin Support
              • May 2000
              • 32996
              • 3.8.x

              #7
              That just means other vB forum on server doesn't have http request sizes hitting varnish cache's preset limits and this particular vB forum does have http request sizes hitting varnish cache limit. The request and response headers for each vB forum may differ in size depending how you have vB forum setup and what other elements on pages i.e. cookie header sizes

              If not using varnish cache, then check your apache configuration i.e. LimitRequestBody http://httpd.apache.org/docs/2.2/mod...mitrequestbody
              Last edited by George L; Fri 23 Nov '12, 6:53am.
              :: Always Back Up Forum Database + Attachments BEFORE upgrading !
              :: Nginx SPDY SSL - World Flags Demo [video results]
              :: vBulletin hacked forums: Clean Up Guide for VPS/Dedicated hosting users [ vbulletin.com blog summary ]

              Comment

              • Paulitos
                New Member
                • Apr 2012
                • 11
                • 4.1.x

                #8
                Originally posted by George L
                That just means other vB forum on server doesn't have http request sizes hitting varnish cache's preset limits and this particular vB forum does have http request sizes hitting varnish cache limit. The request and response headers for each vB forum may differ in size depending how you have vB forum setup and what other elements on pages i.e. cookie header sizes

                If not using varnish cache, then check your apache configuration i.e. LimitRequestBody http://httpd.apache.org/docs/2.2/mod...mitrequestbody
                Thank you for this information

                I just found out the other forum has the same problem ..
                The system designer dek server told me that you have installed:
                DEFLATE + APC (Advanced PHP Cache)

                Comment

                • Paulitos
                  New Member
                  • Apr 2012
                  • 11
                  • 4.1.x

                  #9
                  I have solved.
                  Ther's a problem with MOD SECURITY
                  Thank you

                  Comment

                  • George L
                    Former vBulletin Support
                    • May 2000
                    • 32996
                    • 3.8.x

                    #10
                    Originally posted by Paulitos
                    I have solved.
                    Ther's a problem with MOD SECURITY
                    Thank you
                    related to SecRequestBodyLimit ?
                    :: Always Back Up Forum Database + Attachments BEFORE upgrading !
                    :: Nginx SPDY SSL - World Flags Demo [video results]
                    :: vBulletin hacked forums: Clean Up Guide for VPS/Dedicated hosting users [ vbulletin.com blog summary ]

                    Comment

                    widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                    Working...