For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Sake_Blok's avatar
Sake_Blok
Icon for Nimbostratus rankNimbostratus
Mar 28, 2006

Workaround for invalid 304 content-length

Hi, In a migration towards the BigIP, I encounter a problem with http-304 responses. In the http-header there is a "Content-Length" header with a value greater than 0. The http-rfc clearly states ...
application delivery
dev
devops
iRules
Sake_Blok's avatar
Sake_Blok
Icon for Nimbostratus rankNimbostratus
Mar 30, 2006
Hi Bl0ndie,

 

 

Changing the tcp-payload before the http-parser gets hold of it does indeed do the trick. I now get the http-reponse straight away. Thanks a lot for your help!

 

 

Cheers, Sake

 

 

 

 

PS I reread your initial reply about tcp:collect and realise I misunderstood you. I thought you meant reading out the http-response-data (by tcp-collect) instead of http-resonse-header. Sorry for that...