Discussion Board

Results 1 to 2 of 2
  1. #1
    Super Contributor
    Join Date
    Mar 2003

    A problem with coded/decoded in Nokia Mobile Internet Toolkit

    Posted by Jordan Arribas Aranda, jordan.arribas@eresmas.net
    on April 14, 2002 at 19:41

    My PC runs Windows 98 second edition with Personal Web Server
    My client wap is Nokia Mobile Internet 3.0

    I have written this simple cgi-bin with Visual C++:

    int main(int argc, char* argv[])
    printf("Content-type: text/vnd.wap.wml \n\n"
    printf("<?xml version="putchar(34);printf("1.0"putchar(34);printf("?> \n"
    printf("<!DOCTYPE wml PUBLIC "putchar(34);printf("-//WAPFORUM//DTD WML 1.1//EN"putchar(34);printf(" "putchar(34);printf("http://www.wapforum.org/DTD/wml_1.1.xml"putchar(34);printf("> \n"
    printf("<wml> \n"
    printf("<card id="putchar(34);printf("carta1"putchar(34);printf("> \n"
    printf("<p align="putchar(34);printf("center"putchar(34);printf("> \n"
    printf("<b> \n"
    printf("HOLA \n"
    printf("</b> \n"
    printf("</p> \n"
    printf("</wml> \n"
    return 0;

    I know that the cgi runs well (I can test it for html and asp). The problem is when I try to see it in mode localhost with my cliente wap in my own PC off-line, I get:

    Error: Content could not be encoded by the gateway

    But, Nokia Mobile Internet has its own coded/decoded wml/wmlc, so Why is this?

  2. #2
    Super Contributor
    Join Date
    Mar 2003

    RE: A problem with coded/decoded in Nokia Mobile Internet Toolkit

    Posted by Mobile Internet Toolkit Team, wap.toolkit@nokia.com
    on April 30, 2002 at 14:40

    Hello there,
    I think I can help you with this.

    Though I don't have my own cgi-bin on my local machine that I run my toolkit on, I think I can arm you with some information that can assist you with figuring this out on your own.
    What you need to do is have a look inside your Local Gateway's log file. But first you need to turn on the debugging for it. It's a hack. Just follow the directions below.

    Quit Toolkit.

    Locate the file:
    <Toolkit install path>\WapServer\config\logging.config
    Delete or rename it.

    Locate the file
    <Toolkit install path>WapServer\config.default\logging.config

    Edit it in Notepad.exe
    Change all the line entries in that file that currently have single digit numbers to 7.
    (Don't edit the lines that have two digits.)
    Save the file and start up toolkit again.

    You can now view the error log located at:
    <install dir>\WapServer\logs\error.log. It will show you the raw wml, it will also show you the encoded wml (wmlc).

    The gateway log can be your best friend. It will tell you why it could not encode something.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts