Browse Prior Art Database

Use and Interpretation of HTTP Version Numbers (RFC2145)

IP.com Disclosure Number: IPCOM000002701D
Original Publication Date: 1997-May-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 5 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. C. Mogul: AUTHOR [+4]

Abstract

HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 22% of the total text.

Network Working Group J. C. Mogul

Request for Comments: 2145 DEC

Category: Informational R. Fielding

UC Irvine

J. Gettys

DEC

H. Frystyk

MIT/LCS

May 1997

Use and Interpretation of

HTTP Version Numbers

Status of this Memo

This memo provides information for the Internet community. This memo

does not specify an Internet standard of any kind. Distribution of

this memo is unlimited.

Distribution of this document is unlimited. Please send comments to

the HTTP working group at . Discussions

of the working group are archived at

. General discussions

about HTTP and the applications which use HTTP should take place on

the mailing list.

Abstract

HTTP request and response messages include an HTTP protocol version

number. Some confusion exists concerning the proper use and

interpretation of HTTP version numbers, and concerning

interoperability of HTTP implementations of different protocol

versions. This document is an attempt to clarify the situation. It

is not a modification of the intended meaning of the existing

HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention

of the authors of those documents, and can be considered definitive

when there is any ambiguity in those documents concerning HTTP

version numbers, for all versions of HTTP.

TABLE OF CONTENTS

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.1 Robustness Principle . . . . . . . . . . . . . . . . . . 3

2 HTTP version numbers. . . . . . . . . . . . . . . . . . . . . . 3

2.1 Proxy behavior. . . . . . . . . . . . . . . . . . . . . . . . 4

2.2 Compatibility between minor versions of the same major

version. . . . . . . . . . . . . . . . . . . . . . . . 4

2.3 Which version number to send in a message. . . . . . . . 5

3 Security Considerations . . . . . . . . . . . . . . . . . . . . 6

4 References. . . . . . . . . . . . . . . . . . . . . . . . . . . 6

5 Authors' addresses. . . . . . . . . . . . . . . . . . . . . . . 6

1 In...