Header Examples

Important Note .The header examples and software code below are initial concepts of direction of technology that Vodafone may be pursuing. No changes to your content servers are recommended at this stage.

The table below presents the headers that are used by the WTE to inform content servers of the request path details including which mobile device type is originating the request and which mobile gateway is adapting the internet content for presentation to the device.

Header Example Value Description
User Agent Mozilla/5.0 (X11; U;Linux i686; en-US;
rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 MG
(Novarra-Vision/6.1)
Identitifes the requesting client device as Vodafone's WTE server with web content compatibility equivalent to the Mozilla desktop browser.
Via via 1.1 Novarra-Vision/6.1 REDHAT13.localdomain:3128(squid/2.5.STABLE3) Identifies the proxies and Content Adaptation service from Vodafone or another operator. Note that other proxies in the path will result in a chained value.
x-Device-User-Agent SonyEricssonK800iv/R1CE Browser/NetFront/3.3 Profile/MIDP-2.0 Configuration/CLDC-1.1 Identifies the handset used to make the original request
x-Mobile-Gateway Novarra-Vision/6.1 (VF-UK; Server-Only) Identifies the Content Adaptation service from Vodafone or another operator.

Example Change of Code to PHP Code to Recognise this New Header

The table shows example code with the modification to PHP in order for the content provider to look for and detect the new headers for serving up mobile or PC content.

Sample PHP Code used to get the user agent from a direct handset request:

$headers = apache_request_headers();

$HTTP_USER_AGENT=$headers["HTTP_USER_AGENT"];

Modified PHP code for getting the user agent through the WTE:

<?php
$headers = apache_request_headers();
$HTTP_USER_AGENT=$headers["HTTP_USER_AGENT"];
Modified PHP code for getting the user agent through the WTE:
<?php
 $headers = apache_request_headers();
 
 if (!$headers["x-Device-User-Agent"]) {
  $HTTP_USER_AGENT=$headers["User-Agent"];
  // User-Agent string detected
 } else {
  $HTTP_USER_AGENT=$headers["x-Device-User-Agent"];
  // x-Device-User-Agent string detected
 }
?>

Use of the No-Transform Header to Add Rules to Content

The content provider can also add instructions for mobile operators on what to do with their conent by using the 'No-Transform' header as below.

The content provider can set the parameters below according to what they want to do with their content.

  • The instructions for using No-Transform are easy. To tell the WTE to avoid modifying an item of content in any way, add the following header to the outgoing HTTP response headers:
  • Cache-Control: No-Transform
No-Transform Header Setting Mobile Indicator Present such as .wap, .mobi Content Adaptation type Outcome. Content passed to consumer
True No Pass through PC Content is not modified from the original
True Yes Pass Through Mobile Content is not modified from the original
False (or not set yet) No Internet Content is adapted to fit mobile screens
False (or not set yet) Yes Mobile Content is adapted to fit mobile screens