Confirm
1,567
edits
Changes
→Analyzing for Web Compatibility Issues
== Analyzing for Web Compatibility Issues ==
User Agent String detection on the server side leads to different strategies by the site owner:
* Redirection to a subsection of their domain. Ex: <code>http://example.com/</code> to <code>http://example.com/m</code>
* Redirection to a another domain. Ex: <code>http://example.com/</code> to <code>http://m.example.com/</code>
* Delivering different types of content on the same domain name.
The negotiation is done at the HTTP level.
We can explore what are the influence of an HTTP HEAD or GET and analyzes the answers. [https://bugzilla.mozilla.org/show_bug.cgi?id=901569#c1 An example of analysis]. Often there will be redirects as indicated by the status code <code>301</code>, <code>302</code>, <code>307</code> or <code>308</code>, with a <code>Location:</code> HTTP header <code>Location: http://m.example.com/</code>. (Be careful, some sites send location all in lowercase, in case you are grepping through HTTP headers)
Once we have identified that it is really done server-side, we can add the whiteboard flag [serversidesniff].
==== Tools ====
curl and httpie are two extremely useful tools for analyzing what is happening at the HTTP level. You may also want use things like Firefox Web Developer Tools.
* [http://curl.haxx.se/ curl]
* [http://httpie.org/ httpie]
=== Things to think about when testing ===
* Clearing cookies
* Remove UA override already installed
*
== Finding The Right Contact on a Web site ==
