Passing of the mobile user agent
In addition to sending out a generic identifier, the WTE will also send the mobile device user agent in a 2nd header. The web site owner can make a minor modification modify their site to look for either the mobile or PC header. This change is not recommended yet. The work involved is seen as involving the same effort as adding a new handset UA profile. (An example of PHP code is given in the Headers section). This work is also been driven in the Internet Standards (See The longer term W3C section for details).
Automatic passthrough of mobile sites
- The WTE already recognises several mechanisms by which sites can identify themselves as mobile friendly. This means that content on sites that obey the rules below do not need to be put onto the whilelist as the WTE passes them through without modification. Please check your sites for these parameters before considering adding them to the whitelist
- Correct Sites are passed through the WTE:
- If a domain begins or ends with wap
- If a domain begins with mobile.
- If a domain ends in .mobi
- If a domain starts with m.
- Correct use of the doctype meta tag: 'DOCTYPE html PUBLIC "-//WAPFORUM//DTD XHTML Mobile 1.0//EN" http://wapforum.org/DTD/xhtml-mobile10.dtd'
| Mobile Indicator | Source | Description |
|---|
| Content-Type header | HTTP response -Standard | A site is deemed mobile if the Content-Type header is set to one of the following: | 1 | application/vnd.wap.xhtml+xml |
|---|
| 2 | application/xhtml+xml |
|---|
| 3 | text/vnd.wap.wml |
|---|
|
Use of No-Transform
- The August 2007 rollout adds in improved support for the No-Transform directive in the standard HTTP 1.1 headers. Sites setting this value to 'true' will not be transcoded.
- 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
