Required HTTP headers
Below are lists of the HTTP request and response headers that the Unblu system depends on. While the header names are shown in upper-case here, they are in fact case-insensitive. Any proxy in front of the Unblu system should forward these headers unchanged. Although not all headers will necessarily be required under all circumstances, we nevertheless recommend that you allow all default HTTP/1.1 and all X-UNBLU-* headers to pass in both directions.
Request headers
-
HOST -
ORIGIN -
REFERER -
ACCEPT -
ACCEPT-ENCODING -
ACCEPT-LANGUAGE -
ACCEPT-CHARSET -
COOKIE -
IF-MODIFIED-SINCE -
IF-MATCH -
IF-NONE-MATCH -
AUTHORIZATION -
USER-AGENT -
RANGE -
UPGRADE -
CONTENT-TYPE -
CONTENT-ENCODING -
CONTENT-LENGTH -
CONTENT-DISPOSITION -
CONTENT-RANGE -
TRANSFER-ENCODING -
CONTENT-MD5 -
TRAILER -
KEEP-ALIVE -
CONNECTION -
X-UNBLU-LOCALE -
X-UNBLU-APIKEY -
X-UNBLU-REFERER -
X-UNBLU-CLIENT -
X-UNBLU-PAGE -
X-UNBLU-AREA -
X-UNBLU-SET-COOKIE -
X-UNBLU-COOKIE
Response headers
-
LOCATION -
SET-COOKIE -
SERVER -
CACHE-CONTROL -
PRAGMA -
EXPIRES -
TE -
ETAG -
WWW-AUTHENTICATE -
LAST-MODIFIED -
P3P -
VIA -
ACCEPT-RANGES -
X-UA-COMPATIBLE -
CONTENT-TYPE -
CONTENT-ENCODING -
CONTENT-LENGTH -
CONTENT-DISPOSITION -
CONTENT-RANGE -
TRANSFER-ENCODING -
CONTENT-MD5 -
TRAILER -
KEEP-ALIVE -
CONNECTION -
X-UNBLU-PROXY-ID -
X-UNBLU-AUTH-LOGINNAME -
X-UNBLU-START-TIME -
X-UNBLU-AUTH-ROLES -
X-UNBLU-AUTH-SESSION -
X-UNBLU-AUTH-SESSION-CALL-ORIGIN -
X-UNBLU-BASIC-AUTHORIZATION -
X-UNBLU-SET-COOKIE -
X-UNBLU-COOKIE -
X-UNBLU-CLIENT -
X-UNBLU-PAGE
| We reserve the right to add further headers without prior notice if they are required to fix a bug or to implement a feature. |