Case 3:17-cv-05659-WHA Document 390-10 Filed 03/14/19 Page 1 of 4
`
`Exhibit G
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Case 3:17-cv-05659-WHA Document 390-10 Filed 03/14/19 Page 2 of 4
`Page 2 of 4
`Document 390-10 Filed 03/14/19
`Case 3:17-cv-05659-WHA
`
`Network Working Group
`Request for Comments: 2616
`Obsoletes: 2068
`Category: Standards Track
`
`R. Fielding
`UC Irvine
`
`J. Gettys
`Compaq/W3C
`J. Mogul
`Compaq
`H. Frystyk
`W3C/MIT
`L. Masinter
`Xerox
`P. Leach
`Microsoft
`T. Berners-Lee
`
`W3C/MIT
`June 1999
`
`ÿÿÿÿÿÿ  ÿ
`ÿ

 ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ 
`ÿ
`  ÿÿ
` ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
`ÿ
` ! ÿ"#ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ$ÿ

 %ÿ
`& %ÿ' &
`&ÿ(&)ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ&*+ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ$ÿ, ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ&ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ-ÿ% %ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ+*,(ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ.ÿ,&
` ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ/0ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ1ÿ.&)2ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ, ) ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ(ÿ3
`4.ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ+*,(ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ$
`ÿ555ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ-% 0 ÿ(&
`ÿ1 )ÿ44ÿ-((1*ÿ
`ÿ' & ÿÿ 2 ÿ,ÿ
`ÿÿÿÿ(2 ÿ) 
` ÿ)  ÿ&
`ÿ
` 
` ÿ &
`&ÿ &)ÿ )ÿÿ 2ÿ
`ÿÿÿ
` 
` ÿ)
` %6ÿ&
`ÿ  ÿ )  
`ÿ&
`ÿ  
`ÿÿ
`ÿÿÿ 
` ÿÿ1&ÿÿ ÿ 2ÿ) 
` ÿ 
`ÿÿ 2ÿ7
` 
` ÿ
`ÿÿÿ  ) &ÿ1 )ÿ' &
`&7ÿ8'(9ÿ:ÿÿ 2ÿ &
`& ;& 
`ÿ & ÿ
`ÿÿÿ&
`ÿ & ÿÿ 2 ÿ )ÿÿ9   ! 
`ÿÿ 2 ÿÿ ÿ
`  ÿ
`ÿ% 2 ÿ  )ÿ
`ÿÿÿÿ% 2 ÿ8:ÿ(2ÿ
` 
` ÿ')  %ÿ8555:ÿÿ<ÿ 2 ÿÿ
`ÿ<! &) ÿ
`ÿÿÿÿ(2ÿ-% 0 ÿ(&
`ÿ1 )ÿ8-((1:ÿ ÿ&
`ÿ& )& 
`4ÿ
`ÿÿÿ )ÿÿ   ! 6ÿ)&!& 6ÿ2% &ÿ
`& 
`ÿ
`ÿÿÿ% ÿ ÿ ÿ&ÿ
` )6ÿ & 6ÿ )ÿ2 )2ÿ)&
`ÿ!ÿ ÿÿ
`ÿÿÿ&
`%ÿ &ÿ!%
`ÿ ÿ ÿÿ2% 0 6ÿ )2ÿ&ÿ
`&ÿÿ&
`ÿ
`ÿÿÿ   ! ÿ!=) ÿ&
`&
` ÿ% 6ÿ 2 2ÿ0 
` 
`ÿÿ ÿ
`ÿÿÿ  ÿ 26ÿÿ)ÿ&
`ÿ2&ÿ>?@Aÿ<ÿ& ÿÿ-((1ÿ ÿ
`ÿÿÿ 2ÿ %
`ÿ&
`ÿ
` & 
`ÿÿ& &ÿ
` & 
`6ÿ&
`ÿ% ÿ
`ÿÿÿ ÿ!ÿ!  ÿ
`
`
` %ÿÿ 2ÿ& &ÿ!
`ÿ &
`ÿ
`ÿÿÿÿ-((1ÿ2&ÿ!
`ÿ
`ÿ ÿ!%ÿ 2ÿ4 ÿ!ÿ!&ÿ
`& 
`ÿ
`ÿÿÿ
` & ÿ
`)ÿ55"ÿ(2 ÿ)  )& 
`ÿ
`ÿ 2ÿ )ÿ
`ÿÿÿÿ ÿ&ÿ7-((1*76ÿ&
`ÿ ÿ&
`ÿ & ÿ ÿÿ"#ÿ>++Aÿ
`ÿÿÿÿÿÿ 
`6ÿ ÿ&ÿÿÿÿÿÿÿÿÿÿÿÿ' &
`&ÿ(&)ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ>1&ÿAÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ-((1*ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ$
`ÿ555ÿ
`ÿÿ(&!ÿÿ
` 
` ÿ
`ÿ
`
`(HTTP) is an application-level
`The Hypertext Transfer Protocol
`protocol for distributed, collaborative, hypermedia information
`systems. It is a generic, stateless, protocol which can be used for
`many tasks beyond its use for hypertext, such as name servers and
`distributed object management systems,
`through extension of its
`request methods, error codes and headers [47]. A feature of HTTP is
`the typing and negotiation of data representation, allowing systems
`to be built independently of the data being transferred.
`
`Hypertext Transfer Protocol -- HTTP/1.1
`
`Status of this Memo
`
`This document specifies an Internet standards track protocol for the
`Internet community, and requests discussion and suggestions for
`improvements. Please refer to the current edition of the "Internet
`Official Protocol Standards" (STD 1) for the standardization state
`and status of this protocol. Distribution of this memo is unlimited.
`
`Copyright Notice
`
`Copyright
`
`(C) The Internet Society (1999). All Rights Reserved.
`
`Abstract
`
`HTTP has been in use by the World-Wide Web global information
`initiative since 199@. This specification defines the protocol
`referred to as "HTTP/1.1", and is an update to RFC 2068 [33].
`
`Fielding, et al.
`
`Standards Track
`
`RFC 2616
`
`HTTP/1.1
`
`[Page 1]
`
`June 1999
`
`Table of Contents
`
`

`

`Case 3:17-cv-05659-WHA Document 390-10 Filed 03/14/19 Page 3 of 4
`Case 3:17-cv-05659-WHA Document 390-10 Filed 03/14/19 Page 3 of 4
`15.7 Proxies and Caching ......... cece eee cece cee cere e cece eeeeee 155
`15.7.1
`Denial of Service Attacks on ProxieS............eeeeeeee 156
`16
`Acknowledgments ...... cece eee ee ee cece cece cee eee reece eee eens 156
`17=REFEPENCES 2. cece ccc ce ee eee ee eee eee eee e ence e teens 158
`18 Authors’ Addresses ....... cece cece wee e reer eee reece eee eens 162
`
`xSy \0) 0) <1 0 bk ok=) 164
`19.1
`Internet Media Type message/http and application/http ...... 164
`19.2
`Internet Media Type multipart/byteranges ............e-eeeee 165
`19.3 Tolerant Applications 2... . cece eee ee eee ce ee cece ewww eens 166
`19.4 Differences Between HTTP Entities and RFC 2045 Entities ....167
`
`Fielding, et al.
`
`Standards Track
`
`RFC 2616
`
`HTTP/1.1
`
`[Page 6]
`
`June 1999
`
`19.4.1 MIME-Version 2... .. ccc eee cece eee te cee creer cece eee eeeee 167
`19.4.2
`Conversion to Canonical Form ........... cece cece cere eevee 167
`19.4.3
`Conversion of Date Formats ........ cc eee cece eee ewe eee eee 168
`19.4.4
`Introduction of Content-Encoding ..............e eee e eevee 168
`19.4.5
`No Content-Transfer-Encoding .......... cece eee cece reeeee 168
`19.4.6
`Introduction of Transfer-Encoding ..............eeeeeeeee 169
`19.4.7
`MHTML and Line Length Limitations ...............ceeeeeee 169
`19.5 Additional Features ........ cece cc cece ce ee eee eee cece eens 169
`19.5.1
` CONteNt-DISPOSITION LL. LL Lec ere ewww cere reece cece ee eeee 170
`19.6 Compatibility with Previous Versions .............eeeeeeeeee 178
`19.6.1
`Changes from HTTP/1.0 1... .. ccc ccc cece eee eee reece cere eee 171
`19.6.2
`Compatibility with HTTP/1.@ Persistent Connections ...... 172
`19.6.3
`Changes from RFC 2068 ....... ccc cece eee ee eee eee e eee eeee 172
`722 8 6 (=>:Qe 175
`21
`Full Copyright Statement ........ cece cece ee ee eee eee eee eee eee 176
`
`ÿÿÿ  ÿÿ
`ÿ

ÿ

 ÿ ÿ
`ÿÿÿ   ÿÿÿÿ
`

ÿÿ
` 
`ÿ

ÿ ÿ
` ÿ
`ÿÿÿ ÿÿÿ 
`
` ÿ ÿ
`ÿÿÿ ÿÿÿ
`
`
` 
`ÿ ÿ
`ÿÿÿ ÿÿÿ !ÿ
`
`ÿ "ÿ
`ÿÿÿ #ÿÿÿ$$
`  
`ÿ %ÿ
`ÿÿÿ # ÿÿ& 
`
`ÿ'
`

ÿ()$
`ÿ
`


`*$ÿ

ÿ

$$ 

  *$ÿ %ÿ
`ÿÿÿ # "ÿÿ& 
`
`ÿ'
`

ÿ()$
`ÿ  $

*+)
`


`ÿ ÿ
`ÿÿÿ # ,ÿÿ(
`

ÿ$$ 

  ÿ ÿ
`ÿÿÿ # %ÿÿ 
`
` 
`ÿ-
`
`
` ÿ.((ÿ/  
`ÿ

ÿ0ÿ"1%ÿ/  
`ÿ ÿ
`ÿÿÿ0
` 2ÿ
`ÿ

 ÿÿÿÿÿÿÿÿÿÿÿÿ



ÿ(

ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ3


`ÿ4ÿ
`ÿÿ0ÿ" ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ.((* ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ5
`ÿ ###ÿ
`ÿÿÿÿÿ # % ÿÿÿ'&'/67
`  ÿ ÿ
`ÿÿÿ # % "ÿÿÿ 
`  ÿÿ

 

ÿ0ÿ ÿ
`ÿÿÿ # % ,ÿÿÿ 
`  ÿÿ


`ÿ0

ÿ ÿ
`ÿÿÿ # % %ÿÿÿ&    ÿÿ 
` 6/  ÿ ÿ
`ÿÿÿ # % ÿÿÿ8ÿ 
` 6(


`6/  ÿ ÿ
`ÿÿÿ # % ÿÿÿ&    ÿÿ(


`6/  ÿ #ÿ
`ÿÿÿ # % ÿÿÿ'.('9ÿ

ÿ9
`ÿ9
` ÿ9  

  ÿ #ÿ
`ÿÿÿ # ÿÿ  

ÿ0
`

 
`ÿ #ÿ
`ÿÿÿ #  ÿÿÿ 
` 6 $   ÿ 1ÿ
`ÿÿÿ # ÿÿ$

 +  )ÿ ÿ
`  ÿ7
`  ÿ 1ÿ
`ÿÿÿ #  ÿÿÿ


`ÿÿ.((* 1ÿ  ÿ
`ÿÿÿ #  "ÿÿÿ$

 +  )ÿ ÿ.((* 1ÿ
` 
` ÿ
`  ÿ "ÿ
`ÿÿÿ #  ,ÿÿÿ


`ÿÿ0ÿ"1ÿ "ÿ
`ÿÿÿ"1ÿÿÿ& 
`ÿ ÿ
`ÿÿÿ" ÿÿÿ0 ÿ$) ÿ


`
` ÿ ÿ
`ÿ ÿ&    ÿ
`ÿ ÿ $
`ÿ
`ÿÿÿÿ(
`ÿ.)$
`
`ÿ(


`ÿÿ:.((;ÿ ÿ

ÿ

$$ 

  6
`
`ÿ
`ÿÿÿ$ÿÿ  + 
`2ÿ

+

 
`2ÿ)$
`
`

ÿ 

  ÿ
`ÿÿÿ)
` ÿ.((ÿ

ÿ+
`
` ÿ ÿ 
`ÿ+)ÿ
`ÿ<6< 
`ÿ<
`+ÿ+

ÿ
`ÿÿÿ 

  ÿ 

 
`ÿ 
`ÿ ##1 ÿ(
`ÿ ÿ
`  ÿÿ.((2ÿ
`ÿÿÿ
`
`
`ÿÿ

ÿ.((*1 #2ÿ

ÿ

ÿ $
`ÿ$ÿÿ

ÿ



ÿ


`ÿ
`ÿÿÿ

ÿ
`ÿ& 
`
` ÿ.((* 12ÿ

ÿ
`
`ÿ+)ÿ0ÿ #%ÿ342ÿ $
`ÿ
`ÿÿÿ
`ÿ$ÿ+)ÿ

 ÿ
`


`ÿÿ+
`ÿ ÿ
`ÿ

ÿÿ'&'/6 
`ÿ
`ÿÿÿ
`


`2ÿ 

ÿ
`



  ÿ

+ ÿ
`ÿ



ÿ


`
`ÿ

ÿ
`ÿÿÿ 
`ÿ ÿ
`ÿ
`=
`*
`$ 
`ÿ
`

  ÿ.
`
`2ÿ.((* 1ÿ
`ÿ
`ÿÿÿ ÿ  
` )ÿ


`ÿ ÿ  
`

  ÿ
`ÿ
`
`ÿÿ
`

 

ÿ
`ÿÿÿ$
`2ÿ

 2ÿ
`ÿ
`
`ÿÿ$
` 
` ÿ
`  2ÿÿ 

ÿ
`ÿÿÿ ÿ& ÿ

   2ÿ
`ÿ$ 
`

  ÿÿ $
`
`)6 $
`
` 
`ÿ
`ÿÿÿ

$$ 

  ÿ

 ÿ
`
`
`ÿ>.((* 1>ÿ

ÿ
`
` 


`ÿ

ÿ
`ÿÿÿ$ÿ
`  ÿ


`ÿ ÿ
`ÿÿÿ 

 ÿ

$$ 

  ÿ
`ÿÿÿÿ
`
`
`ÿ
`

ÿ
`!ÿ
`ÿ

$

+  
` ÿ
`ÿÿÿÿ( ÿ$
`  

  ÿ
`
`ÿ
`ÿ$ÿ
`
`
`ÿÿ

ÿ>.((* > ÿ
`ÿÿÿ( ÿ$ÿ  
`ÿ
`ÿ 
` ÿ
`= 
`
` ÿ

ÿ.((* 1ÿ ÿ
`ÿÿÿ
`ÿÿ
`  
`ÿ
`

+
`ÿ $
`
` 

  ÿÿ ÿ
`

 
` ÿ
`ÿÿÿÿ

 

ÿ 

  ÿ)
`ÿ
`= 
`ÿ
`ÿ  

 )ÿ

ÿ $
`ÿ
`ÿÿÿ
`
`

2ÿ   ÿ
`

2ÿ 6
` ÿ $


`2ÿ

ÿ



  ÿ.((ÿ
`ÿÿÿ

ÿ

ÿ$
` 6
` 
`ÿ
`ÿÿ
`ÿ

ÿ
`


`ÿ

ÿ  


`ÿ
`ÿ
`ÿÿÿ$ $
`ÿÿ

ÿ
`=
`ÿ3%4 ÿ&ÿ+ ÿ ÿ
`ÿ  $
`ÿÿ
`
`
` 
`ÿ
`ÿÿÿ$ 
`ÿ+)ÿ
`ÿ? ÿ
` 
`ÿ&
`  
`ÿ:?&;ÿ3,42ÿ

ÿ

ÿ

  ÿ
`ÿÿÿ:?9;ÿ3%4ÿÿ


`ÿ:?8;ÿ3"142ÿÿ  

 ÿ
`ÿ
` 
`ÿÿ ÿ

ÿ
`ÿ
`
`1 Introduction
`
`1.1 Purpose
`
`(HTTP) is an application-level
`The Hypertext Transfer Protocol
`protocol for distributed, collaborative, hypermedia information
`systems. HTTP has been in use by the World-Wide Web global
`information initiative since 199@. The first version of HTTP,
`referred to as HTTP/@.9, was a simple protocol for raw data transfer
`across the Internet. HTTP/1.0, as defined by RFC 1945 [6],
`improved
`the protocol by allowing messages to be in the format of MIME-like
`messages, containing metainformation about the data transferred and
`modifiers on the request/response semantics. However, HTTP/1.@ does
`not sufficiently take into consideration the effects of hierarchical
`proxies, caching,
`the need for persistent connections, or virtual
`hosts.
`In addition,
`the proliferation of incompletely-implemented
`applications calling themselves "HTTP/1.0" has necessitated a
`protocol version change in order for two communicating applications
`to determine each other's true capabilities.
`
`This specification defines the protocol referred to as "HTTP/1.1".
`This protocol includes more stringent requirements than HTTP/1.® in
`order to ensure reliable implementation of its features.
`
`Practical information systems require more functionality than simple
`retrieval,
`including search, front-end update, and annotation. HTTP
`allows an open-ended set of methods and headers that indicate the
`purpose of a request [47]. It builds on the discipline of reference
`provided by the Uniform Resource Identifier (URI) [3], as a location
`(URL)
`[4] or name (URN)
`[20], for indicating the resource to which a
`
`

`

`Case 3:17-cv-05659-WHA Document 390-10 Filed 03/14/19 Page 4 of 4
`Case 3:17-cv-05659-WHA Document 390-10 Filed 03/14/19 Page 4 of 4
`
`Fielding, et al.
`
`Standards Track
`
`RFC 2616
`
`HTTP/1.1
`
`[Page 7]
`
`June 1999
`
`method is to be applied. Messages are passed in a format similar to
`that used by Internet mail
`[9] as defined by the Multipurpose
`Internet Mail Extensions (MIME) [7].
`
`HTTP is also used as a generic protocol for communication between
`user agents and proxies/gateways to other Internet systems,
`including
`those supported by the SMTP [16], NNTP [13], FTP [18], Gopher [2],
`and WAIS [10] protocols.
`In this way, HTTP allows basic hypermedia
`access to resources available from diverse applications.
`
`1.2 Requirements
`
`"SHALL NOT",
`"SHALL",
`"REQUIRED",
`"MUST NOT",
`The key words "MUST",
`"SHOULD",
`"SHOULD NOT",
`"RECOMMENDED",
`"MAY", and "OPTIONAL"
`in this
`document are to be interpreted as described in RFC 2119 [34].
`
`An implementation is not compliant if it fails to satisfy one or more
`of the MUST or REQUIRED level requirements for the protocols it
`implements. An implementation that satisfies all the MUST or REQUIRED
`level and all the SHOULD level requirements for its protocols is said
`to be "unconditionally compliant"; one that satisfies all the MUST
`level requirements but not all the SHOULD level requirements for its
`protocols is said to be "conditionally compliant."
`
`ÿÿÿÿ  ÿ ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿ

`
` ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
` ÿÿ
`ÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿ
`ÿÿÿÿÿ !"ÿÿ "ÿ# ÿ
`$$ ÿ% 
` ÿ
` ÿ$
` ÿÿ
`ÿ&"
` ÿ 
` ÿ "ÿ
`ÿÿÿ !
` ÿ ÿ#'ÿ(  ÿ
`ÿÿ
`ÿ & ÿ#'ÿ ! ÿ% $ $" ÿ
`ÿÿÿ(  ÿ%
`ÿ)* "ÿ+%(%),ÿÿ
`ÿÿÿÿÿÿ
`"ÿ ÿ
`ÿ
`ÿ  ÿ$ " ""ÿ&" ÿ" 
` "ÿ# - ÿ
`ÿÿÿ ÿ
`  ÿ
`ÿ$ "* 
` -
`'ÿ "ÿ" ! ÿ(  ÿ' ÿÿ
`ÿÿÿ !" ÿ$$" ÿ#'ÿ ! ÿ

%ÿÿ..ÿ/ÿ ÿ0ÿ1"$! ÿÿ
`ÿÿÿ
`ÿ23(

ÿ4ÿ$ " ""ÿ(ÿ !ÿ-
`'ÿÿ
`"-ÿ#
`ÿ!'$ 
`ÿ
`ÿÿÿ
` ÿ "ÿ "  ÿ
`5
`
`# ÿ& " ÿ5  ÿ
`$$
` "ÿ
`ÿÿ 6  ÿ
`ÿÿÿÿ! ÿ 'ÿ-" ÿ7%8

7ÿ7%8

ÿ.97ÿ7):8();7ÿ7

3<<7ÿ7

3<<ÿ.97ÿ
`ÿÿÿ7

98<;7ÿ7

98<;ÿ.97ÿ7)9%%).;);7ÿ7%3=7ÿ
`ÿ79(9.3<7ÿÿ !ÿ
`ÿÿÿ"  ÿ
` ÿ "ÿ# ÿ $ ÿ
`ÿ  # ÿÿ ÿÿ/>ÿ
`ÿÿÿÿ3ÿ $ 
` "ÿÿ" ÿ" $
` ÿ&ÿ ÿ&
`ÿ "ÿ
` &'ÿ" ÿ" ÿ " ÿ
`ÿÿÿ"&ÿ ! ÿ%8

ÿ" ÿ):8();ÿ 5 ÿ 6  ÿ&" ÿ ! ÿ$ " ""ÿ ÿ
`ÿÿÿ $  ÿ3ÿ $ 
` "ÿ !
` ÿ
` & ÿ
`ÿ ! ÿ%8

ÿ" ÿ):8();ÿ
`ÿÿÿ 5 ÿ
`ÿ
`ÿ ! ÿ

98<;ÿ 5 ÿ 6  ÿ&" ÿ ÿ$ " ""ÿÿ
`ÿ
`ÿÿÿ "ÿ# ÿ7" "
`'ÿ" $
` 7?ÿ" ÿ !
` ÿ
` & ÿ
`ÿ ! ÿ%8

ÿ
`ÿÿÿ 5 ÿ 6  ÿ# ÿ" ÿ
`ÿ ! ÿ

98<;ÿ 5 ÿ 6  ÿ&" ÿ ÿ
`ÿÿÿ$ " ""ÿÿ
`ÿ "ÿ# ÿ7" "
`'ÿ" $
` 7ÿ
`ÿ/ÿ ""'ÿ
`ÿÿÿÿ!ÿ$ &
` "ÿ ÿ
`ÿ # ÿ"&ÿ ÿ "ÿ & ÿ "ÿ ! ÿ " ÿ
`ÿÿÿ$
`' ÿ#'ÿ$
` $
` ÿÿ
`ÿ"#@  ÿ"&ÿ ! ÿÿ" 
` "ÿ
`ÿÿÿÿ"  "ÿ
`ÿÿÿÿÿÿ3ÿ
`$" ÿ
`' ÿ5 
`ÿ  ÿ 
`#! ÿ# - ÿ -"ÿ$ "
` ÿ
`ÿÿÿÿÿÿ&" ÿ ! ÿ$ $" ÿ"&ÿ" 
` "ÿ
`ÿÿÿÿ 
` ÿ
`ÿÿÿÿÿÿ! ÿ#
`ÿ ÿ"&ÿÿ" 
` "ÿ" ÿ"&ÿ
`ÿ   ÿ
`ÿÿÿÿÿÿ 6  ÿ"&ÿ" ÿ
` !ÿ ! ÿ'
`*ÿ & ÿÿ  "ÿ>ÿ
`ÿ
`ÿÿÿÿÿÿ
`  ÿ5
`ÿ ! ÿ"  "ÿ
`ÿÿÿÿ 6  ÿ
`ÿÿÿÿÿÿ3ÿÿ 6  ÿ 
` ÿ
`ÿ & ÿÿ  "ÿAÿ
`ÿÿÿÿ $" ÿ
`ÿÿÿÿÿÿ3ÿÿ $" ÿ 
` ÿ
`ÿ & ÿÿ  "ÿÿ
`ÿÿÿÿÿÿÿÿ  ÿ ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿ

`
` ÿ
`ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
` ÿ0ÿ
`ÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿ
`ÿÿ
`
`1.3 Terminology
`
`This specification uses a number of terms to refer to the roles
`played by participants in, and objects of,
`the HTTP communication.
`
`connection
`A transport layer virtual circuit established between two programs
`for the purpose of communication.
`
`message
`The basic unit of HTTP communication, consisting of a structured
`sequence of octets matching the syntax defined in section 4 and
`transmitted via the connection.
`
`request
`An HTTP request message, as defined in section 5.
`
`response
`An HTTP response message, as defined in section 6.
`
`Fielding, et al.
`
`Standards Track
`
`RFC 2616
`
`HTTP/1.1
`
`[Page 8]
`
`June 1999
`
`