Sprint Hiding User Agent
I did a search this morning to see if there was anything related to the cookie issue with Openwave software. Instead I found a post from Dennis saying that it appears that Sprint has now followed Vodafone in disrupting the mobile web. Ouch. And their partner in crime? Openwave. I was hoping to find some positive reaction, instead I find a new mention of negative behavior. Damn.
March 18th, 2008 at 7:12 am
We found that sites beginning with “mobile.” are still sent the UA properly. So, one quick hack is to detect the Sprint UA and redirect those clients to an appropriately named host in your domain. Another idea that we’re still testing is to detect the Sprint UA, redirect to a “mobile.” site that does not nothing but redirect back with the real UA encoded as a query parameter in the URL.
March 18th, 2008 at 10:32 pm
[...] developers have heard of the Sprint/Openwave transcoding issue as it’s been picked up by MobHappy, Mike Roewhl, Jason Delport, Semapedia.org and RCR Wireless News. But I’m sure that 100’s of thousands of mobile [...]
March 18th, 2008 at 10:38 pm
[...] developers have heard of the Sprint/Openwave transcoding issue as it’s been picked up by MobHappy, Mike Roewhl, Jason Delport, Semapedia.org and RCR Wireless News. But I’m sure that 100’s of thousands of mobile [...]
March 20th, 2008 at 5:20 am
[...] Mike Rowehl, Techype, RCR Wireless News and Semapedia, amongst others, have picked up on the issue, and [...]
April 15th, 2008 at 7:03 am
[...] developers have heard of the Sprint/Openwave transcoding issue as it’s been picked up by MobHappy, Mike Rowehl, Jason Delport, Semapedia.org and RCR Wireless News. But I’m sure that 100’s of thousands of mobile [...]