| 
 | Please Whitelist This Site?I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)
 If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads. If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK. Thanks for your understanding! Sincerely, Charles KozierokAuthor and Publisher, The TCP/IP Guide
 | 
 
 
   
  
    | 
  
| NOTE: Using software to mass-download the site degrades the server and is prohibited. If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.
 |  |  | 
| 
 
 
 | 
 
 HTTP General Headers
 (Page 3 of 3)
 Upgrade Allows a client device to specify 
what additional protocols it supports. If the server also supports one 
of the protocols the client listed, the server may agree to upgrade 
the connection to the alternative protocol. It indicates the protocol 
to which it is upgrading by including an Upgrade header in a 
101 (Switching Protocols) response to the client. 
This is a hop-by-hop header.Via Included by intermediary devices 
to indicate to the recipient what gateways, proxies and/or tunnels were 
used in conveying a request or response. This header allows easy tracing 
of the path a message took over a potentially complex chain of devices 
between a client and server.Warning Used when needed to provide additional 
information about the status of a message. Many of the defined warning 
header types are related to caching. More than one Warning header 
may appear in a message, and each typically includes a three-digit numeric 
code as well as a plain text messagethe same basic format used 
in HTTP 
response status codes. Table 277 
briefly lists the warnings defined in RFC 2616. 
 Table 277: HTTP Warning Header Codes  
| Warning 
Code | Warning 
Text | Description |  
| 110 | Response is 
stale | Must be included when a response 
provided by a cache is stale (that is, has passed the expiration time 
set for it.) |  
| 111 | Revalidation 
failed | A cache attempted 
to revalidate a cached entry but was unsuccessful, so it returned its 
(stale) cached entry. |  
| 112 | Disconnected 
operation | The cache is disconnected from 
the rest of the network. |  
| 113 | Heuristic 
expiration | Included if 
the cache chose a freshness lifetime of more than 24 hours, and the 
age of the response is also greater than 24 hours. |  
| 199 | Miscellaneous 
warning | Catch-all code for other, non-specific 
warnings. |  
| 214 | Transformation 
applied | Warns the recipient 
that an intermediate cache or proxy applied a transformation of some 
type to change the content 
coding or media 
type of the message or message body. |  
| 299 | Miscellaneous 
persistent warning | Similar to code 199 but indicates 
a persistent warning. | 
 |  Key Concept: HTTP general headers can appear in either an HTTP Request or HTTP Response message. They are used to communicate information about the message itself, as opposed to its contents. General headers are used for functions such as specifying the date and time of a message, controlling how the message is cached, and indicating its transfer encoding method.
 | 
 
 
 
 | 
 | If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support! |  
|  | 
 | 
 
 
 Home - 
Table Of Contents - Contact Us
 
 The TCP/IP Guide (http://www.TCPIPGuide.com)
 Version 3.0 - Version Date: September 20, 2005
 
 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
 Not responsible for any loss resulting from the use of this site.
 |