HTTP request headers

Alokai passes all HTTP request headers to your origin web server and adds additional headers as specified below.

Geo locationri:link

Alokai Cloud sets the following geo location HTTP headers by default:

X-Client-Cityri:link

Name of the city from which the request originated, for example, Mountain View for Mountain View, California. There is no canonical list of valid values for this variable. The city names can contain US-ASCII letters, numbers, spaces, and the following characters: !#$%&'*+-.^_`|~.

Example:

X-Client-City: Warsaw

X-Client-City-Lat-Longri:link

Latitude and Longitude of the city from which the request originated, for example, 37.386051,-122.083851 for a request from Mountain View.

Example:

X-Client-City-Lat-Long: 52.229676,21.012229

X-Client-Geo-Locationri:link

The header is combination of two: {X-Client-Region},{X-Client-City}

Example:

X-Client-Geo-Location: PL,Warsaw

X-Client-Regionri:link

The country (or region) associated with the client's IP address. This is a Unicode CLDR region code, such as US or FR. (For most countries, these codes correspond directly to ISO-3166-2 codes.)

Example:

X-Client-Region: PL

X-Client-Region-Subdivisionri:link

Subdivision, e.g. a province or state, of the country associated with the client's IP address. This is a Unicode CLDR subdivision ID, such as USCA or CAON. (These Unicode codes are derived from the subdivisions defined by the ISO-3166-2 standard.)

Example:

X-Client-Region-Subdivision: PL14

Reference: https://cloud.google.com/load-balancing/docs/https/custom-headers