I should really be running Nextel right now...since I've had to do their jobs for them all this week anyway...  I managed to fix the problem I've been having with thier cellphone webservers, with ABSOLUTELY no help from them.  Not that they haven't tried, but they've not done anything useful except tell me the problem is on my end.  Well it's not, and I told them that, again, and again, and again, and again...  You get the point.  So here was the problem...if you don't care to read technical stuff then I suggest you look for another post to read. 

When a request is made from a wireless device for a website, say www.example.com, you're really not ever talking to that server.  You are actually talking to a WAP gateway that makes the request on your behalf to www.example.com.  If you have more then one computer at home and all of them are on the internet at the same time, then you have a similar setup.  Well WAP takes it one step further and when it gets that page you requested back from www.example.com, it compiles it for you.  On your personal computer the compile is done on your machine, but that would require more processing power and software installed on your phone so it's just easier if the gateway does it for you.  The result is a pretty website on your phone!

Well in our case we were getting the request and sending it back to Nextel's WAP gateway to be compiled and delivered to the phone, but the phone would never display the result, just an error.  We did a line dump on our webserver, which analyzes every single bit of information sent over your internet connection.  We filtered that down to only see the traffic pertaining to our wireless application and examined it line by painstaking line.  Everything checked out as valid, conforming to all internet standards.  So we knew that it was an issue on their end, and I had my suspicions.  It turnes out I was right.  The response headers we sent out (which tell the compiler how to compile everything and where to send it when it's done)  had a line that looked like this:
but every page we saw that worked on nextel didn't have the ; charset=ISO-8859-1 and I thought that might be tripping them up at Nextel.  What we were sending was correct, but I suspected Nextel was out of compliance.  No one there believed me though. They were supposed to move my phone over to their experimental gateway (updated software) at 4:00 am this morning.  So I got up at 5 to check it..but it still didn't work so I gave it another hour..6:00am still no workie.  I then set out to solve the problem myself.  In a matter of two hours I had it working and I was right.  I ran all requests for that particular site through a filter that looks for that response header and rewrites it omitting the semi-colon and beyond.  Wouldn't you know...problem solved.  Nextel is out of compliance...you suck, I rule!