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 29, 2006
Hi Bl0ndie, Uhmm... this application does not send data on the 304, it only adds a "Content-Length" header *as if* it is going to send data. I don't think a TCP::collect will accept a "0" as parameter. But tomorrow I will be on site, I might give it a shot.

 

 

IMHO the only way to solve this issue is to tell the BigIP that there is no data to collect. That way it will not enter the HTTP::collect or TCP::collect that happens between the HTTP_RESPONSE and the HTTP_RESPONSE_DATE (please correct me if my interpretation of how iRules work is incorrect). I'm just not sure if this is possible, and if it is how it can be done...

 

 

 

Cheers, Sake