Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Upgrading to Jetty 9.1

We're using the ram cache feature in big ip - that's what is causing the 1.0 requests: http://support.f5.com/kb/en-us/solutions/public/10000/400/sol10480.html?sr=34761170


2014-01-29 Stefan Magnus Landrø <stefan.landro@xxxxxxxxx>:
I managed to capture the bytes byte array in HttpVersion.lookAheadGet(...)

It clearly says version 1.0. I'll have to check the big ip config.

Stefan

2014-01-29 Stefan Magnus Landrø <stefan.landro@xxxxxxxxx>


>I just pushed a fix for #426870, can you try it out ?

Thanks, Simone! 
Just gave it a shot after building from source. It works perfectly now.
I tried using the snapshot repo first, but apparently that is only built once a day.

There is something I cant really understand, though - why the heck does jetty interpret the request coming from big ip as a http 1.0 request? 
My clients, both my browser and curl use http 1.1 - what could make jetty believe it's a 1.0 request? 
Actually, I'm using a proxy (which only supports http 1.0 it turns out ...), but this is https (using Connect), so the 1.1 request reaches the big ip. In addition the response from big ip clearly states it's a 1.1 request.

BTW - I attached to the actual jvm behind the load balancer, and looked at the ServletRequest in ServletHandler.java. It tells me its a 1.0 request. 
Where is the jetty code that chooses to interpret the request as 1.0, 1.1 etc

Unfortunately I'm struggeling to get access to run a tcpdump - but should get that in the next few days

Stefan
  




--
BEKK Open
http://open.bekk.no

TesTcl - a unit test framework for iRules



--
BEKK Open
http://open.bekk.no

TesTcl - a unit test framework for iRules

Back to the top