Why need a capabilities database, there's a reference in HTTP headers called x-wap-profile

Jul 18, 2009 at 9:58 AM

Accept text/html,text/css,multipart/mixed,application/java-archive, application/java, application/x-java-archive, text/vnd.sun.j2me.app-descriptor, application/vnd.oma.drm.message, application/vnd.oma.drm.content, application/vnd.oma.dd+xml, application/vnd.oma.drm.rights+xml, application/vnd.oma.drm.rights+wbxml, application/x-nokia-widget, */*
 Accept-Charset iso-8859-1, utf-8; q=0.7, *; q=0.7
 Accept-Encoding gzip, deflate, x-gzip, identity; q=0.9
 Accept-Language en;q=1.0,en;q=0.5,ms;q=0.5
 Host gpwap.ebsbd.com
 User-Agent Mozilla/5.0 (SymbianOS/9.2; U; Series60/3.1 NokiaE63-1/100.21.110; Profile/MIDP-2.0 Configuration/CLDC-1.1 ) AppleWebKit/413 (KHTML, like Gecko) Safari/413
 x-wap-profile "http://nds1.nds.nokia.com/uaprof/NE63-1r100.xml"
 X-Nokia-MusicShop-Version 1.0.0
 X-Nokia-MusicShop-Bearer GPRS/3G


I'v written a web application http://wap.gamezilla.com.bd

This app extract the capabilities from the "x-wap-profile" header reference (e.g. parsing the http://nds1.nds.nokia.com/uaprof/NE63-1r100.xml file) when a mobile browser hits my app.

I'v followed the basic architecture of client server model. The client must tell the server who he is and what it's capabilites are. This capabilities can be cached for future use (if the same mobile browser hits again).

Jul 20, 2009 at 7:11 AM


Not all devices have that header unfortunately.

Also, when you are working with Opera Mini, they only send you the original device's agent string in a X- header.  And not all the other headers.

But that "x-wap-profile" can be used to pre-populate a personal database like wurfl/mdbf etc