Browser sniffing
From Wikipedia, the free encyclopedia
Browser sniffing is a common technique used in websites and web applications in order to determine the web browser a visitor is using, and to serve browser-appropriate content to the visitor. This controversial practice is sometimes necessary because of incompatibilities between browsers in areas such as the interpretation of HTML, cascading style sheets (CSS) and the Document Object Model (DOM). While the World Wide Web Consortium maintains up-to-date central versions of some of the most important Web standards in the form of recommendations, in practice no software developer has designed a browser which adheres exactly to these standards; implementation of other standards and protocols, such as SVG and XMLHttpRequest, varies as well. As a result, different browsers will display the same page differently, and so methods have been developed to detect what web browser a user is working with so as to ensure consistent display of content.
Contents |
[edit] Sniffer Methods
[edit] Client-side sniffing
Web pages can use programming languages such as Javascript which are interpreted by the user agent, with results sent to the web server. For example, here is a piece of code that might be used to determine whether a user is viewing a web page with Internet Explorer:
<script type="text/javascript"> var isIE = window.ActiveXObject ? true : false; // ActiveX is only used in Internet Explorer </script>
This code is run by the client computer, and the results sent to the web server. In this example, the client computer is asked to determine whether the browser can use a feature called ActiveX. Since this feature is proprietary to Microsoft, Inc., a positive result will indicate that the client is running Microsoft's Internet Explorer.
[edit] Server-side sniffing
Client-side sniffing makes use of features on the client computer. These features must be available and active in order for the process to work. However, since the web server has no control over whether the client actually has the features available, client-side sniffing is unreliable. It is possible, however, to determine many features of the browser without depending on the client configuration. The web server communicates with the client using a communication protocol known as HTTP, or Hypertext Transfer Protocol. Information communicated between client and server usually includes information about the browser being used to view the web site. See user agent for more details on this.
[edit] Usage
Browser sniffing can produce information on different aspects of the browser used. For example, it can detect which type of browser is being used (e.g., Internet Explorer, Netscape Navigator, Mozilla Firefox, Opera, Apple Safari) and which version of the software the client computer is running. Based on this information, the web server can provide a web page which will be structured appropriately for the user agent. Since browsers can vary significantly in their interpretation of a page, this can be an important consideration for web designers; consequently, there are a large number of scripts for browser sniffing available on the Internet.
[edit] Issues and standards
Browser sniffing has become a controversial practice in light of increasingly common use of alternative browsers such as Mozilla Firefox and Opera. Many websites use browser sniffing to determine whether a visitor's browser is unable to use certain features (such as Javascript, DHTML, ActiveX, or cascading style sheets), and display an error page if a certain browser is not used. However, it is virtually impossible to account for the tremendous variety of browsers available to users. Generally, a web designer using browser sniffing to determine what kind of page to present will test for the three or four most popular browsers, and provide content tailored to each of these. If a user is employing a user agent not tested for, there is no guarantee that a usable page will be served; thus, the user may be forced either to change browsers or to avoid the page. For this reason the World Wide Web Consortium, which sets the standards to be used in presentation of web pages, recommends that web sites be designed in accordance with its standards, and be arranged to "fail gracefully" when presented to a browser which cannot deal with a particular standard.
