Play 2.0 Java - Http 1.0 requests being fulfilled with 1.1 response

[Suchema]

We're sending http 1.0 requests to our play! instance and responses seem to have 1.1 headers. This is causing issues with our proxy (placed in front of our play! instance), as it then causes all sorts of trouble, when the proxy attempts to do things like use keep-alive. Has anyone else seen this issue before? Are we missing some sort of config which needs to be turned on in order to allow us to respond to 1.0 requests in kind?

Here's an example of the sort of thing that we're seeing:

GET /discover/track/40712633 HTTP/1.0
Accept-Encoding: gzip
Host: qa-play1.web
User-Agent: FunkLoad/1.17.0
X-Cluster-Client-Ip: 192.168.x.x


HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Content-Length: 8787

[Julien Tournay]

Hi

You're not missing anything Play is always sending HTT 1.1 responses.

Would it be possible for you to use HTTP 1.1 ?

I don't know the motivations not to support 1.0, but I do know that there's no formal specification of HTTP 1.0, so moving to 1.1 seems like a good move anyway.

jto

[Suchema]

Hi Julien,

Thanks for the prompt reply! Sorry I didn't get back to you earlier, I've only just seen it. Basically we're quite a large mobile media company and some of our legacy clients seem to favour using 1.0. Dropping support for this isn't really something we can do. However, I think we can probably figure out something on our proxy. Thanks for all of the help.

Cheers!

Suche