Forum Discussion

Agathe_309970's avatar
Agathe_309970
Icon for Altocumulus rankAltocumulus
Aug 29, 2018

HTTP 413 error

Hi everyone,

 

I have a specific problem and I want to know if you already see that and if you have a solution.

 

I need to do HTTP POST on a reverse proxy. But I have sometimes the following return : 413 Request Entity Too Large

 

All works fine directly on the serveur. But when I do the HTTP POST on the URL (so the traffic pass by the F5 BIG IP), I have the HTTP error.

 

The file does 10Mo.

 

Thanks a lot in advance.

 

Best regards,

 

Agathe

 

20 Replies

  • I am facing the same issue. Traffic is reaching the Virtual Server (VS) with a pool attached to the actual backend server. The application is working fine, but when trying to upload a 4MB file, I receive the error:


    "Request Entity Too Large – The requested resource does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit."

    Troubleshooting steps attempted:

    1. Disabled renegotiation in the server SSL profile.
    2. Disabled renegotiation in both client and server SSL profiles.
    3. Attached HTTP profiles (LAN Optimized, WAN Optimized).
    4. Applied HTTP Compression, Web Acceleration, and HTTP/2 profiles.
    5. Changed protocol to TCP and UDP.

    Captured a TCP dump, and no RST packets were found, but I observed an "Encrypted Alert."

    Any suggestions for further troubleshooting?

  • I am facing the same issue. Traffic is reaching the Virtual Server (VS) with a pool attached to the actual backend server. The application is working fine, but when trying to upload a 4MB file, I receive the error:


    "Request Entity Too Large – The requested resource does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit."

    Troubleshooting steps attempted:

    1. Disabled renegotiation in the server SSL profile.
    2. Disabled renegotiation in both client and server SSL profiles.
    3. Attached HTTP profiles (LAN Optimized, WAN Optimized).
    4. Applied HTTP Compression, Web Acceleration, and HTTP/2 profiles.
    5. Changed protocol to TCP and UDP.

    Captured a TCP dump, and no RST packets were found, but I observed an "Encrypted Alert."

    Any suggestions for further troubleshooting?

    • Marvin's avatar
      Marvin
      Icon for Cirrocumulus rankCirrocumulus

      My answer is in one of the replies here, if you use apache check the renegotiate buffersize.