Forum Discussion

Manuel_Arme_Netw's avatar
Manuel_Arme_Netw
Icon for Nimbostratus rankNimbostratus
Jun 13, 2024

Problem with big packets using http2

Hi workmates, an application that passes through my F5 BIG-IP, requires for large post request, increasing the maximum header size from the default of 32k to 65k, and everything works perfectly, but ...
BIG-IP
http2
MAXIMUM HEADER SIZE
Manuel_Arme_Netw's avatar
Manuel_Arme_Netw
Icon for Nimbostratus rankNimbostratus

Hi Lucas, maybe I expressed myself wrong, and I didn't give correct information, I meant "large get request" the requests are get and not post, so they don't have body, we have a jwt token that by itself occupies 25 Kb, plus other data that adds up and exceeds 32 Kb, unfortunately I didn't find any logs of error in the Big IP.

I have the client error which is this (when http2 is used):

this is a curl that simulates the same size as the get


Failed sending HTTP request: Header overflow
* Failed sending HTTP request
* Connection #0 to host "our.domain.com" left intact
curl: (55) Failed sending HTTP request: Header overflow

 

the fact is that, unlike the http profile, there isn't parameter for the "Maximum Header Size"

 

I hope I have explained myself well now, and I hope you have a solution 😀

Lucas_Thompson's avatar
Lucas_Thompson
Icon for Employee rankEmployee
Aug 02, 2024

OK great! Sounds like you have a good method to reproduce the error. Can you share precisely:

  1. What is the curl command you use to create this behavior
  2. What is the virtual's HTTP profile configuration? Use "tmsh list ltm virtual <your virtual>" to obtain the profile names, then use "tmsh list ltm profile http <your http profile name>".

In this way, we can run a quick test in a lab to be more sure the solution is correct.