Designing Evolvable Web APIs with ASP.NET
by Glenn Block, Pablo Cibraro, Pedro Felix, Howard Dierking, Darrel Miller
Appendix B. HTTP Headers
| Header | Description | Reference |
| Gives instructions to caching mechanisms that the request/response passes through related to its cachability. | http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-21#section-7.2 |
| Gives options that are specific to the current connection and should not be passed on to proxies. | http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-21#section-6.1 |
| Specifies the date and time the message originated. | http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-21#section-8.1.1.2 |
| Specifies to caches that they should always revalidate a response they have cached. It exists for backward compatibility with HTTP 1.0 clients and is deprecated in HTTP 1.1 by the | http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-21#section-7.4 |
| Indicates if the message body has had any transformation applied to it in order to transfer it between the sender and the recepient. | http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-21#section-3.3.1 |
| Allows the client to specify that it would like to use additional protocols if the server is willing to switch. | http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-21#section-6.3 |
| Used by gateways and proxies, it contains the intermediate protocols and recepients between the client and the server on requests, and the server and client on responses. This header is very useful in a response from a |