Confirm
1,567
edits
Changes
→Analyzing for Web Compatibility Issues
=== Server Side User Agent Detection ===
User Agent String detection on the server side leads to different strategies by the site owner:. They are used for delivering content to specific browsers and/or specific devices. The negotiation is done at the HTTP level.
* Redirection to a subsection of their domain. Ex: <code>http://example.com/</code> to <code>http://example.com/m</code>
* Delivering different types of content on the same domain name.
We can explore what are the influence of an HTTP HEAD or GET and analyzes the answers. 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)
=== Redirection based on Geolocation ===
=== Missing vendor extensions ===
==== CSS vendor extensions ====
==== JavaScript vendor extensions ====
=== Things to think about when testing ===
