Professional mobile web browser Use WAP emulator to develop mobile sites View mobile web pages on nokia, sony ericsson, siemens   WAP simulator allows to test WAP PHP services

Online documentation

How to...
Advanced functions

What is WAP?

WAP (Wireless Application Protocol) is a protocol stack designed in 1998-2001 to view small pages (decks) on mobile terminals. The constraints of mobile terminals include small display and limited user input facilities, narrowband network connection and limited memory and computational resources.

The most of Internet-capable mobile phones support WAP stack version 1.3. The specification defines a protocol for the connection of mobile terminals with Internet. This protocol (WTP/WSP) is based on UDP and it is adapted for narrowband connections. In particular, the most of HTTP-headers and XML-tokens are compressed into the binary form. The conversion between WTP/WSP and HTTP protocols is performed by a WAP gateway.

Besides the network protocol, the WAP Forum designed a markup language to write content for mobile phones. WML (Wireless Markup Language) is an XML language, it includes some HTML tags, but it also contains tags specific for mobile devices. The WML file (or deck) consists of several cards. Each card contains text, images, input fields, etc. To view WML-pages, the mobile phone must be equipped by a WML-browser.

The current version of WAP is 2.0. The WAP 2.0 specification allows mobile devices to access Internet directly (without WAP gateway). Since the connection bandwidth of modern bearers (EDGE or 3G) much exceeds the bandwidth of traditional GPRS or CSD bearers, direct access to the Internet becomes more and more popular.

The markup language of WAP 2.0 is XHTML Mobile Profile 1.0 which is a subset of XHTML and may be viewed by an ordinary web browser. The most mobile browsers supporting XHTML may also view simple HTML documents.

What is WAP Proof?

The key feature of the WML language is that it does not define how the card will be rendered by a WML browser. The reason is that mobile devices may have different screen sizes, different color depths, etc. The same WML page should be rendered both on a small black-white screen and on a smartphone (for instance, 320x240 color) screen. This feature of WML makes the design of mobile pages difficult, since the designer must test the WML-site on a number of mobile phones and must therefore pay for devices themselves and WAP-access.

The WAP 2.0 specification determines the so-called mobile XHTML language, which is similar to HTML and allows to use style sheets. The idea of mobile XHTML is to simplify the design of mobile content, forcing the pages to be rendered similarly on all mobile terminals. However, not all WAP-capable devices support XHTML. The MIME-type of mobile XHTML pages is application/xhtml+xml, and the user can not be sure that the page is designed for a mobile phone. Another problem is that the XHTML pages may also not render similarly on different mobile terminals.

The purpose of WAP Proof is to view WML 1.3 and XHTML-MP documents on different devices. It is intended for designers of mobile content. In order to debug WML or XHTML content, the user of WAP Proof should not load the same document to a number of phones, he may switch the terminal by a mouse click.

WAP Proof works over HTTP like an usual HTML browser. It has some useful features simplifying the design of mobile content, such as XML syntax checking, logging of HTML traffic, direct editing of HTTP request.

Getting started

When you start WAP Proof, you see the phone window at the left-hand side and several windows at the right-hand side. The toolbar (at the top) contains the most frequently used commands. The address box is the place where the URL of a mobile-oriented document should be typed. The status bar (at the bottom) contains status information and errors.

To download the document, type the URL in the address box and press ENTER or click a green "Go" button. If your internet connection is set properly, the source of the WAP page will be downloaded in a source window and the HTTP messages will be seen in a traffic window.

After the document is downloaded, WAP Proof checks its content type. If the content type (MIME type) is text/vnd.wap.wml, the WML page is parsed by the XML parser. The XML documents are also parsed by WAP Proof, so you can check their syntax as well. If there are parse errors, you can read error messages in the message window (they are highlighted by a red background).

If the document contains no critical errors, the current WML card is rendered on the screen of the mobile device. Click buttons on the phone keyboard by a mouse or use keys UP, DOWN, ENTER, ESC, BACKSPACE to navigate through the WML document.

If the content type of the document is application/vnd.wap.xhtml+xml and the currently selected phone supports XHTML, the XHTML page is rendered on the screen. The navigation through the document is similar to the navigation through WML cards. The plain HTML pages intended for mobile phones can also be rendered by WAP Proof.

Phone window

The phone window is located at the left-hand side of the application window. This is a main child window of the application, you can not close it. The phone window contains the currently selected mobile phone. When the WML page is downloaded and it contains no critical errors, it is rendered on a screen of a mobile phone.

To navigate through WAP pages, click phone keys by the left mouse button. The behaviour of the virtual phone is similar to the behaviour of a real phone; in particular, click several times to enter a key in the input field.

When the phone window achieves the keyboard focus, you may use keyboard to navigate through WML cards. Keys LEFT, RIGHT, UP, DOWN, ENTER, ESC, BACKSPACE may be used for the navigation. You can also use the mouse wheel to scroll the page up and down. When you are in the input field, you can type the value instead of using a mouse and a virtual phone keyboard.

Source code window

In the source code window you can browse the contents of the downloaded text file (text/*) or an XML document. For a WML file, this window contains a source code of the deck. The window is read-only; to change the contents of the WML deck, you should modify the file on a server. The XML syntax of the document is highlighted. To toggle highlighting of XML elements, change the appropriate flag in WML section of the IDH_OPTIONS dialog. The text in the source code window may be selected by a left mouse button and copied to the clipboard as in ordinary text editor.

You can toggle wrap mode of the viewer by clicking "Toggle wrap" button on the toolbar or by selecting menu item "View"/"Wrap mode".

The special characters (entities) may be viewed as a symbols. To view special characters, click "Decode entities" button on the toolbar or select "View"/"Decode entities" menu item.
Note: switch off decoding entities when copying the text to the clipboard if you intend to save the selected text as a WML, XHTML or HTML file. Otherwise, the text will be saved "as is" and will contain no more entities.

When you download binary data, the source code window will contain the warning message highlighted by yellow color. You can save the binary file to the local disk by using "Save" button or menu item. To open the binary data using the default shell handler, click "Open in shell" button or select "Tools"/"Open in shell" menu item.

Traffic window

The traffic window contains information on the HTTP transactions performed by the user. Each string of the traffic window contains time, connection ID and log message. Errors are highlighted by yellow background, the information on transactions is green and the additional debug information is not highlighted. The log level may be chosen by selecting a combo box "Log level" in Options dialog.

The text in the traffic window is read-only. You can select and copy the text as in ordinary text editor. You can also toggle wrap mode of the viewer by clicking "Toggle wrap" button on the toolbar or by selecting menu item "View"/"Wrap mode".

The number of lines in the traffic window is limited. This number may be changed in Options dialog (parameter "Log entries"). The traffic window may be cleared by selecting Tools/Clear log menu item.

Message window

When a WML or XHTML document is loaded, it is parsed by an XML parser. If there are parse errors, they are outputted in the message window and highlighted by a red background. If the document contains errors, the page may be rendered incorrectly or even may not be rendered at all (the corresponding message appears in the status line).

The error message contains the string where an error is encountered. You can highlight the string containing an error in a source code window by double-clicking the string in the message window.

WML context window

The WML context is a set of variable-value pairs set during the navigation over WML document(s). The context variables are set by <setvar> tag or when user inputs data in the form tags. When a new document is to be opened, the variables are substituted in the source document.

In the WML context window you can see the non-empty context variables in the form

The window is read-only; to change the context variables, you should navigate through WML deck. The text in the WML context window may be selected by a left mouse button and copied to the clipboard as in ordinary text editor.

To clear the WML context, you must select menu item "Tools"/"Clear WML context".

Edit HTTP request

Besides the URL, the HTTP request consists of the method (GET or POST), HTTP headers (containing information about the user-agent, accepted MIME types, etc.) and query (set of variable/value pairs). Query is intended for the transition of some information to the server. According to the HTTP protocol, it may be transferred to the server either as a part of the URL (GET request) or as the request body (POST request).

This information is hidden for user, he can not change the HTTP parameters directly. The query and method is set up by the browser in accordance with the user input in the form fields. However, direct access to this information is very useful for content designers for the debugging of their scripts.

WAP Proof allows the user to modify the request method and HTTP headers and to edit the query. To enter "HTTP request properties" dialog, you must click on the "HTTP request properties" button (to the right from the URL box) or select Tools/Request properties menu item.

The dialog consists of two tabs allowing user to modify headers or query.

Edit HTTP query

In the "Edit HTTP query" tab you can change the location of the file, HTTP method and edit the HTTP query. According to the HTTP protocol, the query may be transferred to the server either as a part of the URL (GET request) or as the request body (POST request, application/x-www-form-urlencoded). The query is always URL-encoded.

To add, edit or remove query variables, use buttons at the right-hand side. The encoding for non-ASCII symbols is chosen below the white list box containing query variables.

To change the encoding of the query, use the "Encoding" combo box and "Encode"/"Decode" buttons with triangles. The field containing the encoded query is read-only, you should edit the variables instead of encoded query. However you can select and copy the contents of this field as in ordinary text editor.

Modify HTTP headers

HTTP headers are the attribute/value pairs containing information about the browser and the request. Some headers are specific for a mobile terminal:
User-Agent: This attribute contains browser name. For mobile terminal, the value of User-Agent consists of the model of mobile device and the WML browser version(s), separated by a slash (/).
Profile: This attribute contains the web-address for the phone profile. The profile is an XML file containing information about the phone capabilities: screen size, resolution, char set, etc.

The tab "HTTP headers" consists of two lists: permanent and temporary. The permanent headers are valid for all HTTP requests; they are specific for a mobile terminal. The temporary headers are valid only for one request.

You can add, delete or edit HTTP header using the buttons at the right-hand side. Switching between temporary and permanent headers is made by a mouse click inside a corresponding list box.

Note: there are some headers which are included in the HTTP request but they can not be edited:
Host: contains host name
Content-Type: application/x-www-form-urlencoded (for POST requests)
Content-Length: body length (for POST requests)

HTTP headers containing information about the caching are also managed automatically.

Configure WAP Proof

The configuration dialog is opened by selecting Tools/Options menu item. The dialog consists of three tabs:
General - HTTP log, history and application window settings;
HTTP - HTTP proxy server and cache settings;
Browser - XML/WML settings.

To save configuration, click OK. If you wish to discard changes, click Cancel. The options are stored in the configuration file wproof.ini. To access more options, you can edit this file instead of using "Options" dialog.

General settings

This tab allows to modify HTTP log, history and application window settings.
Log level - Output level in the traffic window (all information including debug information, events or only errors);
Log entries - number of strings in the traffic window;
Clear log - clears the contents of the traffic window;
History entries - number of URLs saved in the address box;
Clear history - clears all URLS saved in the address box;
Remember window positions - if checked, the desktop configuration as well as the position of the application window is saved on exit;
Check size of application window - if checked, you can not make application window too small (the smallest size is limited by visibility of a toolbar and is approximately 400x300);
Show tips at startup - check this box if you wish to read tips at startup.
Prompt on large HTML pages - if checked, a warning is displayed if you try to open a too large web page (the maximal web page size is configured in the edit window "Max page size").

HTTP settings

This tab allows to modify HTTP proxy server and cache settings.
Use proxy server - select this check box if you have a proxy server for your HTTP connection; type host, port, user and password in the input fields below;
Use cache - use cache for HTTP pages.

Browser settings

This tab gives you access to the WML and XML settings.
View images - uncheck this box to disable images in the WML card;
Play animations - uncheck this box to disable animations in the rendered page;
Recover XML errors - if checked, some XML errors are recovered and you can see the contents of a WML document even if it contains errors;
Highlight WML syntax - toggles the highlighting of the WML elements in the source code window by colors;
Follow WML events - uncheck this box to disable automatic processing of the WML navigation events (onenterforward, onenterbackward, ontimer);
Follow redirects - uncheck this box to disable automatic HTTP redirection;
Timer tick - you can change the default duration of the WML timer tick ("ontimer" event).

Use bookmarks

You can remember the URL of your favorite documents by using bookmarks. Type the URL in the address box and select Bookmarks/Add bookmark menu item or click "Add bookmark" button. Write the title of the bookmark, which will be visible in menu "Bookmarks" and press OK. The bookmark will be saved. To download the document, select the corresponding title in menu "Bookmarks".

You can edit bookmarks by selecting Bookmark/Edit bookmarks menu item. Use buttons to the right of the list box to add, edit or delete bookmarks.

Arrange the layout

The WAP Proof workspace consists of the following windows:
Phone window containing the picture with the current mobile device and the rendered WML card or XHTML page;
Source code window containing the source code of the WML document or content of the downloaded text file;
Message window containing XML errors;
WML context window containing currently set WML context variables;
Traffic window containing information about HTTP transactions.

The size and position of all windows may be changed. If you wish to arrange all the windows on the application client area, choose Window/Arrange menu item.

All windows except the phone window may be closed. You can either close them by clicking on a "Close" button at the right top corner, by using buttons "Source", "Messages", "WML context", "HTTP Traffic" on a toolbar, or by selecting the corresponding items in menu View.

Open and save file

The WAP Proof may view mobile-oriented pages not only in the web, but it can also view documents on a local disk (work offline). Select File/Open menu item or click "Open file" button to load the data from a disk. Since the encoding of the document is not set up by the HTTP protocol, you should select the appropriate encoding in the "Open file" dialog box. Click OK to load the file. The address box now contains the local URL of the file beginning with "file://".

The file opened by WAP Proof may be saved on the local computer. To save the file, set focus to the source code window and select File/Save menu item or click "Save file" button. Type the required file name and select a proper encoding for text data.

Note: You must not change encoding for binary data.

Editor commands

Child windows of WAP Proof are read-only. To change the contents of the WML deck, you should modify the file on a server.

The text in the window may be selected by clicking a left mouse button and dragging the mouse. The following editing commands are available (menu Edit or buttons on the toolbar):
Select all - select all contents of the window;
Copy - copy selected area to the clipboard (CTRL-C or CTRL-INSERT);
Search - search for a substring in the window (CTRL-F).

Navigate through mobile-oriented pages

To open the new URL, type the address in the address box and press "Go" button. The downloading of the document will start. The following navigation commands are available:
Stop - click the "Stop" button or select File/Stop menu item to stop downloading; when the document is completely downloaded, this button (and menu item) is disabled;
Reload - click the "Reload" button or select File/Reload menu item to refresh the currently downloaded document;
Back - click the "Back" button or select File/Back menu item to download the previous document;
Forward - click the "Forward" button or select File/Forward menu item to download next document in download stack (this option is enabled only if you have selected "Back");

When you are using the mobile device to navigate, commands "Back" and "Reload" may be also done using the phone keyboard. The navigation stack on the real mobile phone may be cleared by the attribute "newcontext" of the <card> tag. When you are trying to go back beyond the card with newcontext set to "true", you will receive a warning message. Click YES to go back.

The WML redirection (attributes "ontimer", "onenterforward" and "onenterbackward" of the <card> tag) is done automatically unless this feature is disabled (flag "Follow WML events" in the WML tab of the Options dialog). To switch off HTTP redirection, use the flag "Follow redirects" in the same tab.

Change the mobile device

The layout of the mobile-oriented page differs for different mobile devices. For example, the screen size and color depth may vary. The rendering of WML tags may also differ, for instance, the paragraph with disabled wrapping (attribute "nowrap" of <p> tag set to "true") may appear as a long scrollable line (Nokia 5100), as a set of frames (Sony Ericsson T610/T630) or as a marquee (running text) (Siemens S45). The WML document you design should look well on the most of mobile phones.

To check the appearance of the mobile-oriented document on another mobile phone, select the desired device in menu Device. The skin will change and the document will be reloaded.

The HTTP attributes are phone-specific. For example, the User-Agent attribute contains the model of the mobile device. Therefore, you can use WAP proof to design a phone-specific content of the site.

View special characters

Since WML and XHTML are XML languages, such characters as '<', '>', '"' and some other characters are unsafe. That is, you can use these characters only in XML elements. If you would like to display an unsafe symbol on the page, the hexadecimal encoding (for instance, '"' is encoded as &#x22; or as &#34;) or using entities is required. The following entities are defined in WML:
&quot; - quotation mark
&amp; - ampersand
&apos; - apostrophe
&lt; - less than
&gt; - greater than
&nbsp; - non-breaking space
&shy; - soft hyphen
Note: other entities defined in HTML are NOT defined in WML! XHTML Mobile Profile defines some more special characters, such as single and double quotation marks, spaces, etc.

If you are writing a page containing non-ASCII symbols, you may also use hexadecimal encoding. In this case, the source code of the page becomes unreadable. To view encoded characters, set focus to source code window and check the button "Decode entities" on the toolbar or select View/Decode entities menu item.

Note: switch off decoding entities when copying the text to the clipboard if you intend to save the selected text as a WML or XHTML file.

Document encoding

If your WML document contains non-ASCII symbols (for example, accented letters), the encoding must be set up to view the document properly. The standard encoding for mobile phones is UTF-8. The document encoding may be defined by HTTP protocol (attribute Content-Encoding) and in the first string of the XML document (attribute "encoding"). You can change the encoding manually by selecting one of the encodings in menu View/Encoding.

If you load the file from a local computer, you must choose the appropriate encoding in the Open dialog.

Sending POST request

To send POST request to server, you need to setup query and HTTP method in HTTP request properties dialog and press ENTER or click "GO" button. The progress is reflected in the traffic window.

After the file has been downloaded, the request properties are reset to default (GET method). If you wish to resend the request, select Tools/Restore request menu item. The method and query will be restored. To change, use HTTP request properties dialog.

User-Agent profile

The WAP specification introduces the User Agent Profiling framework. User Agent Profiling framework offers means to organize and utilize user agent information for further use, such as content formatting for the different client devices. User Agent Profiles are composed of capabilities of the client device hardware and software plus the preferred settings of the user. The User Agent Profile is stored in the Internet in a form of XML file. The mobile browser sends the information about the profile in the HTTP header; the value of the "Profile" attribute contains the URL of the User Agent Profile.

To download and view the User Agent Profile for a currently selected mobile terminal, select "Tools/View Profile" menu item. The XML file containing the User Agent Profile will be downloaded in a source code window.

Open binary data

WAP Proof may open WML and XHTML documents as well as view other text data. If you download a binary file, it cannot be viewed (you will see a yellow warning message in the source code window). To open binary data, press "Open in Shell" button on the toolbar or select Tools/Open in shell menu item. The default Windows handler for this content type will be loaded.

Note 1: If you try to open a Windows-executable file, you will get a warning message. Some executable files may contain viruses or trojans and may damage your computer. If you still wish to execute the file, click YES.

Note 2: WAP Proof uses MIME type of the file to choose the handler. The file extension is considered only if no appropriate handler was found or the file is loaded from a local computer.

If you wish to view an HTML document, you can also click "Open in Shell" button. The HTML page will be opened in your default HTML browser. Please note that if the currently selected phone supports XHTML, WAP Proof will try to render it in the phone window. If the document is not designed for mobile phones, the rendering may take a long time and may be incorrect.

Resource viewer

The resource viewer contains the resources (images, animations, style sheets) used in the downloaded document. To view the desired resource, double-click the list item or select the list item by a single mouse click and press ENTER. The image or animation resource will be opened in an image viewer, and the CSS resource will be opened in a CSS viewer window.

This feature is available in the Professional version.

Image viewer

If you click the image resource in the resource viewer, it will be opened in the image viewer window. The title of this window contains the URL of the resource. To increase or decrease the image size, click the buttons below the image. The window may be resized. The image may be copied to clipboard by selecting the appropriate menu item.

If you open a new document, all resource windows will be closed.

This feature is available in the Professional version.

CSS viewer

If you click the style sheet resource in the resource viewer, it will be opened in the CSS viewer window. This window may be used in the same manner as the source code window: you can select and copy window text, scroll the text up and down, toggle wrap mode. The syntax of the cascade style sheet is highlighted if you set the appropriate flag in the "Browser settings" tab of the "Options" dialog. Please note that the syntax is highlighted only if the content type of the resource is "text/css".

If you open a new document, all resource windows will be closed.

This feature is available in the Professional version.

Indenting the document

The WML or XHTML document dynamically created by a server script may be unreadable at the client side because of the lack of formatting. To make the downloaded document readable and to simplify the tracking of bugs, you must select the "Indent document" item in the "Tools" menu. The document will be indented so that the tree structure of the XML can be seen.

The CSS documents may also be indented in the same manner.

To save the indented document, simply select the "Save" menu item or press the "Save" button on a toolbar. To restore the document to its unindented form, you must reload it.

The CSS resource opened in a separate window may also be indented.

The menu item "Indent document" is available, when the source viewer window is active. To activate the window, click the window title.

This feature is available in the Professional version.

Copying the page text

Select the "Edit"/"Copy text" menu item to copy the textual contents of the downloaded page to the clipboard. The clipboard will contain only the plain text. To copy the whole rendered page to the clipboard, use the "Edit"/"Copy page" menu item.

The menu items responsible for copying page contents are grayed unless the phone window is activated. To activate the window, click the window title.

This feature is available in the Professional version.

Copying the page contents

Select the "Edit"/"Copy page" menu item to copy the rendered page to the clipboard as an image. To copy the textual contents of the page to the clipboard, use the "Edit"/"Copy text" menu item.

The menu items responsible for copying page contents are grayed unless the phone window is activated. To activate the window, click the window title.

This feature is available in the Professional version.

Purchase WAP Proof

WAP Proof is a commercial software. You may evaluate the full version of WAP Proof for a 15-day trial period free of charge. If you wish to use the software for an unlimited period, you must buy it. Online purchase is available at

After the registration, you receive an e-mail containing your name and registration code. To enter the registration information, click "Enter code" button on a nag screen, enter your name and registration and click "OK". Please note that, to make your copy available for other users of your computer, you must have administrator rights during the registration.

Note: type your name exactly as you have typed it in the purchase form. Otherwise, the registration may fail.

To complete the registration, you must activate your copy. The activation of the software is based on a unique (anonymous) ID of your computer and verifies that you do not install more copies than you have purchased.

To activate your copy online, just click the "Activate" button on the activation screen.

If your computer has no access to the Internet, you may activate WAP Proof by e-mail. Click the "Generate e-mail" button, copy the address, the subject and the code to your e-mail program, and send the e-mail to us. If your activation is successful, you will get the reply containing the activation code (the e-mail activation is processed manually so the reply will be delivered within one business day). Click the "Enter code" button and complete the activation.

The registration and activation screens are accessible from the "Help" menu.

Technical support

The request for technical support may be done by e-mail (see readme.txt for details) or by submitting a form at Your request for support will be processed as soon as possible.

Report a bug

Bugs may be reported by e-mail (see readme.txt for details) or by submitting a form at In your bug report, please specify the version of WAP Proof you are using, the version of Windows, the mobile device and the document causing an error (the reference or the document itself).


This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. ( The SSL implementation is written by Eric Young ( The Windows-specific SSL code is written by Tim Hudson (

This product includes LibXML written by Daniel Veillard ( The Windows-specific LibXML code is written by Igor Zlatkovic (c) 2000-2006.

This product includes libpng (copyright (c) 2001-2006 Greg Roelofs,

This product includes libiconv (copyright (c) 1998, 2007 Free Software Foundation, Inc.,

This product includes zlib (copyright (c) 1995-2005 Jean-loup Gailly and Mark Adler,

Browse WAP pages by different mobile phones


Web-design: Baltic Favorite © 2006
© 2004-2008 Litemobile Software. All rights reserved