F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

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 Colin,

 

 

Yes, I did try "HTTP::release", as well as "HTTP::collect 0". The first did not help, the BigIP still waited for the announced amount of data. The second gave an error, the parameter needs to be greater than 0.

 

 

I have a case for this issue also (C260102), there seem to be some CR's, but unfortunately it seems our configuration (on 9.1.1) is still vulnerable. It also looks like this is not fixed in later releases, hence the iRule-workaround...

 

 

So far, the only thing that stops the BigIP from waiting for the content that neven comes is "HTTP::disable", but I'm afraid that'll break other stuff.

 

 

 

Cheers, Sake