Browser sniffing: Difference between revisions
→Client-side sniffing: rm redundant |
Use section and Issues and standards say almost the same thing |
||
| Line 16: | Line 16: | ||
===Server-side sniffing=== |
===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 [[computer configuration|configuration]]. The web server communicates with the client using a [[Protocol (computing)|communication protocol]] known as [[HTTP]], or Hypertext Transfer Protocol. Information communicated between [[client (computing)|client]] and [[Server (computing)|server]] usually includes information about the browser being used to view the [[web site]]. See [[user agent]] for more details on this. |
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 [[computer configuration|configuration]]. The web server communicates with the client using a [[Protocol (computing)|communication protocol]] known as [[HTTP]], or Hypertext Transfer Protocol. Information communicated between [[client (computing)|client]] and [[Server (computing)|server]] usually includes information about the browser being used to view the [[web site]]. See [[user agent]] for more details on this. |
||
==Use== |
|||
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]], [[Google Chrome]], [[Opera (web browser)|Opera]], [[Safari (web browser)|Apple Safari]]) and which version of the [[software]] the [[client (computing)|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 designer]]s; consequently, there are a large number of scripts for browser sniffing available on the Internet and even commercial solutions such as BrowserObject or BrowserHawk. |
|||
==Issues and standards== |
==Issues and standards== |
||
Revision as of 19:48, 9 May 2011
 |
Browser sniffing is a 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 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.
Sniffer Methods
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:
<script type="text/javascript"> var isIE = window.ActiveXObject ? true : false; </script>
This code is run by the client computer, and the results are used by other code to make necessary adjustments on client-side. 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 likely running Microsoft's Internet Explorer.
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.
Issues and standards
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. The World Wide Web Consortium, which sets standards for the construction 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.