tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: about the version of HTTP protocol
Date Fri, 08 Jan 2010 21:59:50 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter,

On 1/8/2010 3:00 AM, Peter Chen wrote:
> I am using Tomcat 5.5.26, and the configuration of Connector is
> like this:
> 
>     <Connector port="8088" protocol="HTTP/1.1"

[snip]

> It's clear that the HTTP protocol version is HTTP/1.1. The web
> service provided by this Tomcat will be used all over the world. So,
> maybe someone will use HTTP/1.0 or HTTP/0.9.
> 
> I want to know does this Tomcat support HTTP/1.0 or HTTP/0.9 protocol.
> Pleas help me make sure of it.

Take a look at http://tomcat.apache.org/tomcat-6.0-doc/config/http.html
for the meaning of the "protocol" attribute.

If you read further down in that document, you'll see this section:

"
HTTP/1.1 and HTTP/1.0 Support

    This Connector supports all of the required features of the HTTP/1.1
protocol, as described in RFC 2616, including persistent connections,
pipelining, expectations and chunked encoding. If the client (typically
a browser) supports only HTTP/1.0, the Connector will gracefully fall
back to supporting this protocol as well. No special configuration is
required to enable this support. The Connector also supports HTTP/1.0
keep-alive.

    RFC 2616 requires that HTTP servers always begin their responses
with the highest HTTP version that they claim to support. Therefore,
this Connector will always return HTTP/1.1 at the beginning of its
responses.
"

So, in a nutshell: HTTP/1.1 is backward-compatible with HTTP/1.0.
HTTP/1.0 is nominally backward-compatible with HTTP/0.9, but nobody uses
0.9 so you shouldn't really worry about that.

> I think the version of used HTTP protocol is determined by
> browser, is it right?

It's determined by both client and server. The client is required to
advertise the highest level of HTTP it supports in the request, as is
the server in the response. The server should adjust the response
characteristics to match that of the client to the best of its ability.

For your purposes, I don't believe any additional configuration is
necessary to support these legacy clients.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktHqtYACgkQ9CaO5/Lv0PCVdwCgtc0rP/q9xf9CmU+hJVscaIbQ
G0gAmwaZkxhI/68qBV7bmnbA+k1hw5rA
=JlBC
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message