Overview of HTTP Headers
This appendix lists HTTP headers used in the Blueprint environment that may be of interest to third-party developers. The Content-Type header must be included when your server sends Blueprint pages.
Request Headers (Sent by Yahoo!)
| Header | Description |
|---|---|
| Accept | Content type. |
| Accept-Language | RFC 4646/4647 language code. |
| Geo-Country | ISO 3166 country or UN M.49 region code. |
| Geo-Position | User's current location (latitude/longitude). |
| Location | URI for redirecting request. |
| User-Agent | Yahoo! server directly making request. |
| X-Carrier-Info | Client's carrier network. |
| X-Client-Accept | Media types supported by software client. |
| X-Client-Info | Client software accessing the application. |
| X-Client-Misc | Additional client information (e.g. screen type). |
| X-Device-Accept | Media types supported by hardware device. |
| X-Device-Info | Client's hardware device. |
| X-Device-User-Agent | Device's original user agent. |
| X-Forwarded-For | Chain of IP addresses (proxy connections). |
| X-Forwarded-Host | Host name for gateway (Web renderer) requests. |
| X-Geo-Location | User's current location (street address). |
| X-Request-Id | Unique ID for request tracking. |
Response Headers (Sent by Blueprint Application)
| Header | Description |
|---|---|
| Cache-Control | Caching directives. |
| Content-Length | Size of message body, in bytes. |
| Content-Type (required) | Content type (application/x-blueprint+xml). |
| ETag | Entity tag for conditional reuse of cached data. |
| If-None-Match | List of current versions (okay to use from cache). |