Maybe you would like to know…it doesn’t return the mobile version at all within Windows Phone.
It is a good thing I was using wifi too…it needed to download so much…over 1 MB insane!
Fiddler’s report:
Request Count: 113
Unique Hosts: 17
Bytes Sent: 60,384 (headers:60,156; body:228)
Bytes Received: 1,268,283 (headers:40,492; body:1,227,791)
ACTUAL PERFORMANCE
--------------
Requests started at: 05:26:17.517
Responses completed at: 05:26:34.189
Sequence (clock) duration: 00:00:16.6719744
Aggregate Session duration: 00:00:23.567
DNS Lookup time: 73ms
TCP/IP Connect duration: 2,231ms
HTTPS Handshake duration: 33ms
RESPONSE CODES
--------------
HTTP/200: 112
HTTP/502: 1
RESPONSE BYTES (by Content-Type)
--------------
application/x-javascript: 428,446
image/pjpeg: 310,622
image/jpeg: 146,526
image/png: 122,999
text/html: 104,487
text/css: 47,987
text/javascript: 44,505
~headers~: 40,492
application/javascript: 15,196
image/gif: 6,807
application/x-www-form-urlencoded: 216
ESTIMATED WORLDWIDE PERFORMANCE
--------------
The following are VERY rough estimates of download times when hitting servers based in WA, USA.
US West Coast (Modem - 6KB/sec)
RTT: 11.30s
Elapsed: 232.30s
Japan / Northern Europe (Modem)
RTT: 16.95s
Elapsed: 237.95s
China (Modem)
RTT: 50.85s
Elapsed: 271.85s
US West Coast (DSL - 30KB/sec)
RTT: 11.30s
Elapsed: 55.30s
Japan / Northern Europe (DSL)
RTT: 16.95s
Elapsed: 60.95s
China (DSL)
RTT: 50.85s
Elapsed: 94.85s
Well the first thing to figure out is whether the redirection script is in the server or client code. So to start it seems like the best thing to do is go through the JavaScript files and search for window.location. See if that yields any redirection logic. If not than the logic is most likely in the server-side code. In which case you would need to locate that and modify it. Look through all the files for whatever the function name is in asp to redirect or set headers. Not familiar with asp so couldn’t tell you.
Though I have always believed this whole thing is destined for failure. The idea of inspecting headers and redirecting is fundamentally flawed itself. Not from the stand point of using separate sites necessarily but because there so many different devices and headers are not consistent plus always changing. So it really is just all a cluster f**k to begin with. However, if it is something that you *must do than well locating the redirection logic is the first step.
Inspection of the meta tags revealed the CMS that is most likely being used:
