Rodger Castle wrote:
The first step is setting up a static wml file - a tiny hello world file named index.wml (make sure it has a .wml extension). Now try to view that. If that doesn't work, you're problem has nothing to do with mod_perl. If it does, then you've got more work to do. And if you've done this already... sorry to waste your time. :) And if your phone has a normal web browser instead of a WAP browser, ignore this entirely... but I'm assuming you're using a WAP browser.I've been pulling my hair out this evening trying to resolve a problem serving content to a cell phone.
Phone is a LG VX-4500. I've written a simple handler as a start to just send "Hello" to the phone along with a Content-Length and Connection: Close header but the phone just times out. With a browser, all is well. File-based (non mod_perl) content gets to the phone fine, it's only the mod_perl content that is timing out. I can see the requests coming and going in the logs. It looks like the data just never gets sent back to the phone.
Running: Debian Sarge Apache 2.0.52 mod_perl2
Any thoughts on this would be appreciated.
Rodger
I'm far from an expert, as I just started playing with WAP and WML a few weeks ago, but unless content-type isn't coming out correctly, your issue isn't mod_perl related. You're best bet is to hit a WAP/WML-specific forum or mailing list for help.
Ultimately, when in doubt, try things in static pages first, and when you get that working, try the same thing under mod_perl. If that doesn't work, use telnet to connect to your web server and request the document to see what exactly it's doing. After that, it's likely to be obvious.
-ofer
