Debugging WURFL
by Luca Passani
passani at eunet dot no
If you point to a WALL-based application with a web browser, you are
most likely to receive the CHTML version (unless you have
tweaked your WURFl version). While this is good to quickly get a glimpse
of the application flow, it may be useful to quickly
look at which mark-ups is provided to other devices.
One possibility is to use one of the tricks described in the
tutorial,
Debugging WALL Applications.
Another quick and dirty
possibility is to use the 'UA' (UA=User Agent) parameter
in the query string to override the User-Agent header. While WALL
normally derives the User Agent string from the HTTP Request,
defining UA will override this. In practice, an URL like the following
will force your application to return WML code (specifically
the one usually returned to a Nokia 7110):
http://localhost:8080/wurfl/wall/menu.jsp?UA=Nokia7110
More examples can be found here (these are real, thank
again to David Johanson for hosting a live instance
of the WALL library):
UP.Browser/4 = WML 1.1
http://www.tr-x.com:8080/wurfl/wall/menu.jsp?UA=UP.Browser/4
UP.Browser/5 = WML 1.2
http://www.tr-x.com:8080/wurfl/wall/menu.jsp?UA=UP.Browser/5
UP.Browser/6 = XHTML MP
http://www.tr-x.com:8080/wurfl/wall/menu.jsp?UA=UP.Browser/6
portalmmm = CHTML (Imode Europe)
http://www.tr-x.com:8080/wurfl/wall/menu.jsp?UA=portalmmm
Of course, these are just examples, since you can user any UA String
to simulate the request of any device.
Enjoy!
|
|
