Skip to main content

HTTP headers

Clonable adds a number of additional HTTP headers that you can use to identify traffic from Clonable. You can use these headers, for example, to choose the right thank you page in your integration with your payment platform.

Security

Make sure requests are not signed in any way and that other parties can also send these headers. When you use these headers for security sensitive actions, make sure you only accept them from our servers. We keep a list of IP addresses here.

Server headers

Below is the list of headers that are added to the request before it is sent to your server. For the list of headers that are sent along with the request to the client, you can look here.

Accept-Encoding

The header Accept-Encoding will never be present on requests from Clonable. This is because our system does not yet work with GZIP or Brotli data. Connections between the visitor and Clonable do support GZIP.


Clonable Crossborder clone

The header Clonable-Crossborderclone includes the domainname of the clone. The domainname includes www if this is the standard setting of the site. For clones from clones, this header will include the domainname of the clone of the original (and not the domainname of the clone from the clone).

Example
Clonable-Crossborderclone: www.clonable.net

Clonable-Original-Language and Clonable-Target-Language

The headers Clonable-Original-Language and Clonable-Target-Language include the ISO 639-1 country codes of the language from the original site and the target language of the clone respectively. These headers are present on both translating clones and non-translating clones (where they will have the same value).

Example
Clonable-Original-Language: nl
Clonable-Target-Language: de

Clonable-Quota-Reached

The header Clonable-Quota-Reached includes a boolean value (true or false) a value indicating whether the maximum number of characters for this clone has been reached. This header can be used, for example, for internal monitoring to keep an eye on whether the clone is still creating new translations.

Example
Clonable-Quota-Reached: false
Notifications

In the future, we want to offer our customers the option to receive notifications when their quota is full. This will make the header less useful. We have no plans to remove this header at this time.


Clonable-Request-ID

The header Clonable-Request-ID includes an unique ID for the request. This header is a hex representation of a 16 byte long string. This id is especially useful during debugging or a general recognition of Clonable traffic.

Example
Clonable-Request-ID: 90d6a07531c59bca6ce7423b640de2e8

X-Device (Outdated)

The header X-Device has two possible values: Mobile or Desktop. The value is Mobile when the clients user-agent includes iphone, android or mobile (not-capitalizable) and Desktop in all other cases. This header is marked as outdated and can be deleted from requests at any moment.

Example
X-Device: Mobile

X-Forwarded-For

The header X-Forwarded-For includes the received value of the X-Forwarded-For header followed by the IP-address of the client separated by a comma. If the X-Forwarded-For header was not present in the incoming request, it will only include the IP-address of the visitor.

Example
X-Forwarded-For: 198.51.100.56

X-Forwarded-Proto

The header X-Forwarded-Proto always includes the vale https. Indeed, Clonable does not allow visitors to visit clones over unsecured connections and will always redirect such requests to a secure HTTPS connection first.

Example
X-Forwarded-Proto: https

X-Real-IP

The header X-Real-IP includes the IP address of the client that sent the request.

Example
X-Real-IP: 198.51.100.56

Client headers

Below is the list of headers that are added to the responses sent to visitors.

Clonable-Processing-Time

The header Clonable-Processing-Time contains the time in milliseconds it took Clonable to translate the page. This is mainly used internally to monitor the speed of our platform. This header is only present for translated responses.

Example
Clonable-Processing-Time: 34

Clonable-Request-ID

The header Clonable-Request-ID contains a unique id for the request. This header is a hex representation of a 16 byte long string. This id is especially useful during debugging or a general recognition of Clonable traffic. This header is added to all responses.

Example
Clonable-Request-ID: 90d6a07531c59bca6ce7423b640de2e8

Clonable-Server

The header Clonable-Server contains the hostname of the server that processed the request.

Example
Clonable-Server: gw1.ams.cinfra.net

Content-Language

The header Content-Language contains the ISO 639-1 language code of the clone. This header is added to inform browsers and search engines of the language of the web page content. This header is added to all responses.

Example
Content-Language: en

Server

The header Server always contains the value Clonable.

Example
Server: Clonable