I appreciate your attempt at debunking my claim, but I am no noob at this, sir!
You seem to have missed the major point here:
I am able to log-on to Cricket's servers usign my VERIZON WAP settings and the VERIZON login settings.
Although both are set to
http://homepage, that doesn't explain why my Verizon WAP settings (gateway info) and Veriozon login settings (
[email protected]) would connect me to Cricket's network.
For those who don't know what I'm saying, let me explain this another way:
Here is Cricket's WAP info:
--Server name: wap.cricket.com
--User name:
[email protected]
--Password: cricket
And Verizon's:
--Server name: gw.vzwwap.com
--User name:
[email protected]
--Password: vzw
What I'm saying is that the latter Verizon WAP settings connect's me to the web PERIOD: Given the above phenomena, the fact that
http://homepage which resolves to
http://wap.cricket.motricity.com is entirely moot, other than it seems as though it should resolve to Verizon's WAP portal instead, but it doesn't.
While this makes sense that I am on Cricket's network at the time I connect, it doesn't explain why Cricket's servers should honor my WAP request when I am requesting an
entirely different WAP server with entirely different login credintials.
Does everyone understand what I am saying now??? :silly: