Home
| | Sitemap
||Page number :16
Programmer's Guide Nokia WAP Server API 1.1 page 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17
previous || guide home || next
5.8 WAP MIME types
WAP defines its own MIME types for WAP-specific content types. Typically, a WAP terminal can accept the following MIME types:
| application/vnd.wap.wmlc | Encoded WML |
|---|---|
| application/vnd.wap.wmlscriptc | Encoded WMLScript |
| image/vnd.wap.wbmp | WAP graphics format |
Note that all WAP terminals may not support WMLScripts or bitmaps. In addition to these, some more specialised content types can be accepted:
When a request comes to the Nokia WAP Server, it adds some accepted content types to the request before forwarding it to the servlet. The following content types are added: In addition to these, the MIME types defined in the MIME type mapping (see 5.6.2) are added to the request's accept header.
| MIME type | Description |
| text/vnd.wap.wml | Textual WML. If the servlet sets the content-type to this type, the Nokia WAP Server automatically encodes the given WML page before it is sent to terminal. |
| text/vnd.wap.wmlscript | Textual WMLScript. If a servlet sets the content-type to this, the Nokia WAP Server automatically compiles and encodes it before sending it to the terminal. |
| text/html | Textual html. If a servlet is willing to return HTML, the Nokia WAP Server will convert it to WML and encode it before sending it to the terminal. |
Terminals may accept multipart content types. If a servlet replies with a multipart response containing e.g. textual wml and textual wmlscript, the Nokia WAP Server can correctly encode the individual subparts with the appropriate encoder.
Note that the WAP protocols and the Nokia WAP Server can be used to deliver any content type to the WAP terminal. So, the Nokia WAP Server's content delivering ability is not limited to WAP content types.
Programmer's Guide Nokia WAP Server API 1.1 page 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17
previous || guide home || next