Forum Discussion
Agathe_309970
Altocumulus
AltocumulusHTTP 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 r...
Marvin
Cirrocumulus
CirrocumulusSo after analysis with F5 support and case was escalated and their statement was "Likely the problem is there because when the configures VS to re-encrypt traffic (clientssl and serverssl profiles attached), the SSL handshake is slightly different than when fastL4 is used and this is expected"
So guess what i forward traffic on port 80 and it works no issues with bigger file uploads, only when enabling SSL this occurs. Looking still for the root cause here.
boneyard
MVP
MVPif you are already in contact with F5 support let them come up with the root cause, they are best suited to investigate things like this.
if they don't want to and have a valid reason, you seem quite close with a root cause then capture the traffic and look for the differences.
- Marvin
ok guys I have the anwser, on apache server there exist SSLRenegBufferSize parameter https://httpd.apache.org/docs/current/mod/mod_ssl.html#sslrenegbuffersize
When you have F5 configured as SSL bridging by default it renegotiates SSL in serverssl profile, which could cause the error in apache ssl.log AH02018: request body exceeds maximum size (131072) for SSL buffer.
There are 3 possible fixes for it:
1. Turn off renegotiation in server SSL profile.
2. Change SSLRenegBufferSize to higher on Apache server
3. Change Renegotiate size in serverssl profile the same as ApacheWhat I tried was increasing the SSLRenegBufferSize parameter in Apache, but there are several solutions provided by F5 support.
- boneyard
thank you very much for replying with the answer.