One Javascript

Introducing Y!OS 1.0 - live today!

2008-12-20T11:32:00.001-08:00

Earlier this month, we introduced a revamped universal profile to all Yahoo! users – but that was just the tip of the iceberg. With the new profile page, you got a peek at our open vision, but today’s Yahoo! Open Strategy (Y!OS) 1.0 platform launch gives you something to get your hands on. Today we’re making Y!OS a reality for developers through the release of the Yahoo! Application Platform (YAP) , Yahoo! Social Platform (YSP) and Yahoo! Query Language (YQL). Now, anyone on the web has access to Yahoo!’s tools and data to start building applications for Yahoo!’s vast audience and the web beyond.

Yahoo! Social Platform
The Yahoo! Social Platform (YSP) consists of a suite of REST-based social APIs from Yahoo! including: Profiles, Connections, Updates, Contacts and Status. These services will make it possible for you to write social applications either on Yahoo! using the Application Platform or on your own website. We are releasing a PHP SDK an a Flash SDK to help you access these web services. Because we make use of standard OAuth and REST (both XML and JSON), standard libraries can also be used.

Yahoo! Query Language (YQL)
YQL is a new web service API that lets you access other web services using a SQL-like language rather than typical programmatic access. You can think of it as a command line version of Pipes. Its goal is to make data from Yahoo! as well as from across the internet universally accessible through a single common interface.

Yahoo! Application Platform (YAP)
YAP will soon become the mechanism for distributing your application to millions of users on Yahoo!’s homepages, media sites, and mail properties, some of the most trafficked sites on the Internet. The initial release supports a few programming models including:
- Developer hosted execution of applications with access to Yahoo's Social APIs and YQL;
- Support for OpenSocial's JavaScript API; and
- Support for server-side YML tags.

Today we are launching the platform itself; for now, we hope you’ll start building apps to view in thecanvas view. We will keep you updated on the rollout schedule for embedding third-party applications within the pages of Yahoo!'s properties. In the meantime we’d love to hear from you and see what you’re building.

Yahoo! values user security and privacy. We've put several mechanisms in place to keep YAP secure, so that people are always in control of the data they put into the system:
- All HTML, CSS & JS code will be run through Caja . Check the release notes for what capabilities are supported;
- Users have the option of not sharing their data with their connections applications;
- Spam protection is in place around messaging, invites, and updates.

OAuth
YAP, YSP, and YQL are all accessed using the open standard OAuth to authenticate both the developer and the 3rd-party (user) on whose behalf the developer is accessing the data. This ensures that our users are always in control over who can access their data.

What’s next?

In 2008, it’s been all about building the base platform. For the rest of the year and into 2009, we’ll focus on integrating the platform into rest of Yahoo!. As we rewire Yahoo! in this way, you’ll see two major things start to happen:

1. Users will begin to experience what we call a “social dimension” across Yahoo!.

We’ll activate our network horizontally across Yahoo!. Yahoo! Mail and Yahoo! Messenger will encourage users to connect with the people that they care the most about. For example, Mail will incentivize connections by enabling users to filter their inboxes to see emails just from social connections. And Mail, Messenger, the front page of Yahoo!, and My Yahoo! will allow people to see things their connections have been doing across Yahoo! and the web. Finally, Yahoo!’s media properties (Sports, Music) will contribute to social relevancy by encouraging users to share experiences with each other.

2. We’ll continue to open Yahoo! to developers and publishers like never before.

By opening up, we create experiences that give people choice about the content they consume. We’re committed to giving our users what they want, where and with whom they want it. We’ll continue opening the UI of places like My Yahoo!, the Yahoo! homepage (www.yahoo.com), and Mail to 3rd party applications via YAP, so our users gain access to the best and liveliest of the web. And our Social Platform APIs give developers across the web the tools and data services to create rich experiences for this newly active social user base. You’ll be able to publish activity stream information via Updates and reach users across the Front Page, Messenger and Yahoo! Mail.

This launch also marks Yahoo!’s first implementation of OpenSocial support. As a founding member of the OpenSocial Foundation, Yahoo! is committed to supporting the complete OpenSocial specification and is working with the community to expand the spec to include OSML and OpenSocial templates. In addition, we are currently implementing a Shindig-based OpenSocial container which will allow us to provide full support for the OpenSocial REST Protocols and thus for Portable Contacts. To learn more about YAP and OpenSocial, please visit the OpenSocial blog.

Developers everywhere benefit from the fact that Yahoo!'s audience is worldwide. Our platform is fully internationalized from the start for use in 31 countries. And we’re growing. Come along and go global with Yahoo!.

We hope that you’ll check out the documentation and start creating apps today.

Sam Pullara
Vice President, Yahoo! Application Platform

Google and Yahoo host third-party JavaScript libraries

2008-12-13T10:22:00.000-08:00

Google to host a number of JavaScript libraries

Posted on: Wednesday, May 28th, 2008 at 2:01 pm

Google just announced their AJAX Library API, where Google will host many major JavaScript frameworks for you, such as jQuery, Prototype, Mootools, Dojo, etc.

This will allow you to write web pages that refer to those scripts rather than copies on your own site, reducing your bandwidth, but also leveraging the infrastructure capabilities of Google, such as their content distributed network (which means users would be served those files from a location much closer to them), properly compressed, minified, cacheable files, etc.

In addition, if your visitors have been to other sites using the same technique, they would not need to download the same libraries all over again, and with increasingly rich web sites, these files can get quite large...

A number of months back, Yahoo was the first to announce something like this when they said they would host their YUI library for you so it is good to see others getting into this.

HTTP Status Code Definitions

2008-09-29T11:09:00.000-07:00

Top error codes:

200 OK
206 Partial request OK
302 Redirect
304 Not Modified - OK to use cached file
403 Forbidden - Protected page
404 Not Found

Your Web server thinks that your URL has been temporarily redirected to another URL. The client system is expected to immediately retry the alternate URL.

302 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:
Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '302'.

part of Hypertext Transfer Protocol -- HTTP/1.1
RFC 2616 Fielding, et al.
10 Status Code Definitions
Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required in the response.
10.1 Informational 1xx
This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions.
A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent.
Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a
proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).)
10.1.1 100 Continue
The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section8.2.3 for detailed discussion of the use and handling of this status code.
10.1.2 101 Switching Protocols
The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
The protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features.
10.2 Successful 2xx
This class of status code indicates that the client's request was successfully received, understood, and accepted.
10.2.1 200 OK
The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:
GET an entity corresponding to the requested resource is sent in the response;
HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
POST an entity describing or containing the result of the action;
TRACE an entity containing the request message as received by the end server.
10.2.2 201 Created
The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. The response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server SHOULD respond with 202 (Accepted) response instead.
A 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created, see section 14.19.
10.2.3 202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.
The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.
10.2.4 203 Non-Authoritative Information
The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).
10.2.5 204 No Content
The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant.
If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent's active view.
The 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.
10.2.6 205 Reset Content
The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.
10.2.7 206 Partial Content
The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field (section 14.35) indicating the desired range, and MAY have included an If-Range header field (section 14.27) to make the request conditional.
The response MUST include the following header fields:
      - Either a Content-Range header field (section 14.16) indicating         the range included with this response, or a multipart/byteranges         Content-Type including Content-Range fields for each part. If a         Content-Length header field is present in the response, its         value MUST match the actual number of OCTETs transmitted in the         message-body. 
      - Date 
      - ETag and/or Content-Location, if the header would have been sent         in a 200 response to the same request 
      - Expires, Cache-Control, and/or Vary, if the field-value might         differ from that sent in any previous response for the same         variant 
If the 206 response is the result of an If-Range request that used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response MUST include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
A cache MUST NOT combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see 13.5.4.
A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.
10.3 Redirection 3xx
This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection.
      Note: previous versions of this specification recommended a       maximum of five redirections. Content developers should be aware       that there might be clients that implement such a fixed       limitation. 
10.3.1 300 Multiple Choices
The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content- Type header field. Depending upon the format and the capabilities of
the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.
If the server has a preferred choice of representation, it SHOULD include the specific URI for that representation in the Location field; user agents MAY use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.
10.3.2 301 Moved Permanently
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
      Note: When automatically redirecting a POST request after       receiving a 301 status code, some existing HTTP/1.0 user agents       will erroneously change it into a GET request. 
10.3.3 302 Found
The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
      Note: RFC 1945 and RFC 2068 specify that the client is not allowed       to change the method on the redirected request.  However, most       existing user agent implementations treat 302 as if it were a 303       response, performing a GET on the Location field-value regardless       of the original request method. The status codes 303 and 307 have       been added for servers that wish to make unambiguously clear which       kind of reaction is expected of the client. 
10.3.4 303 See Other
The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response MUST NOT be cached, but the response to the second (redirected) request might be cacheable.
The different URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
      Note: Many pre-HTTP/1.1 user agents do not understand the 303       status. When interoperability with such clients is a concern, the       302 status code may be used instead, since most user agents react       to a 302 response as described here for 303. 
10.3.5 304 Not Modified
If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields.
The response MUST include the following header fields:
      - Date, unless its omission is required by section 14.18.1 
If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by [RFC 2068], section 14.19), caches will operate correctly.
      - ETag and/or Content-Location, if the header would have been sent         in a 200 response to the same request 
      - Expires, Cache-Control, and/or Vary, if the field-value might         differ from that sent in any previous response for the same         variant 
If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.
If a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.
10.3.6 305 Use Proxy
The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses MUST only be generated by origin servers.
      Note: RFC 2068 was not clear that 305 was intended to redirect a       single request, and to be generated by origin servers only.  Not       observing these limitations has significant security consequences. 
10.3.7 306 (Unused)
The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.
10.3.8 307 Temporary Redirect
The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI.
If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
10.4 Client Error 4xx
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents SHOULD display any included entity to the user.
If the client is sending data, a server implementation using TCP SHOULD be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted by the HTTP application.
10.4.1 400 Bad Request
The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
10.4.2 401 Unauthorized
The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43].
10.4.3 402 Payment Required
This code is reserved for future use.
10.4.4 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
10.4.6 405 Method Not Allowed
The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.
10.4.7 406 Not Acceptable
The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically. However, this specification does not define any standard for such automatic selection.
      Note: HTTP/1.1 servers are allowed to return responses which are       not acceptable according to the accept headers sent in the       request. In some cases, this may even be preferable to sending a       406 response. User agents are encouraged to inspect the headers of       an incoming response to determine if it is acceptable. 
If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.
10.4.8 407 Proxy Authentication Required
This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field (section 14.33) containing a challenge applicable to the proxy for the requested resource. The client MAY repeat the request with a suitable Proxy-Authorization header field (section 14.34). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" [43].
10.4.9 408 Request Timeout
The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.
10.4.10 409 Conflict
The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body SHOULD include enough
information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type.
10.4.11 410 Gone
The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise.
The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion of the server owner.
10.4.12 411 Length Required
The server refuses to accept the request without a defined Content- Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.
10.4.13 412 Precondition Failed
The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.
10.4.14 413 Request Entity Too Large
The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server MAY close the connection to prevent the client from continuing the request.
If the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again.
10.4.15 414 Request-URI Too Long
The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI.
10.4.16 415 Unsupported Media Type
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
10.4.17 416 Requested Range Not Satisfiable
A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)
When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource (see section 14.16). This response MUST NOT use the multipart/byteranges content- type.
10.4.18 417 Expectation Failed
The expectation given in an Expect request-header field (see section 14.20) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
10.5 Server Error 5xx
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents SHOULD display any included entity to the user. These response codes are applicable to any request method.
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
10.5.2 501 Not Implemented
The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
10.5.3 502 Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
10.5.4 503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
      Note: The existence of the 503 status code does not imply that a       server must use it when becoming overloaded. Some servers may wish       to simply refuse the connection. 
10.5.5 504 Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
      Note: Note to implementors: some deployed proxies are known to       return 400 or 500 when DNS lookups time out. 
10.5.6 505 HTTP Version Not Supported
The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described in section 3.1, other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server.

Internet Explorer 8 and Maximum Concurrent Connections

2008-09-25T12:53:00.000-07:00

Internet Explorer 8 and Maximum Concurrent Connections

As defined in 1999 (RFC 2616) “clients that use persistent connections should limit the number of simultaneous connections that they maintain to a given server. A single-user client SHOULD NOT maintain more than 2 connections with any server or proxy. A proxy SHOULD use up to 2*N connections to another server or proxy, where N is the number of simultaneously active users. These guidelines are intended to improve HTTP response times and avoid congestion.” Since developers are using AJAX or AJAX-like requests to update a Web page the http limits are discussed more and more.
Currently WinInet limits connections per server with a registry setting (for both, http 1.1 and 1.0). You can simply change the value and have the possibility to connect to more than one server at the time. Other Web browser have limited the concurrent connections to other values. Opera lets you change the value through the Preferences dialog box, look under Advanced –> Network. Firefox users just type about:config in the address bar and hit enter. Then type connections into the filter field. The setting your looking for is network.http.max-persistent-connections-per-server.
Now, Internet Explorer 8 changes the maximum number of concurrent connections:
Version HTTP 1.0 server (broadband) HTTP 1.1 server (broadband) HTTP 1.0 server (narrowband) HTTP 1.1 server (narrowband)
Internet Explorer 7 and earlier 4 2 4 2
Internet Explorer 8 6 6 4 2
What does this mean for end-users? Well, it is much easier for a client to initiate more than two downloads (in the past you had to open Internet Explorer again to start a new instance to get two more connections). You may expect higher number of downloads at the same time instead of several two-paired downloads on your Web server.
What about XMLHttpRequest? You’re now able to initiate up to 6 AJAX requests to the same Web server. Do you really need this? In my eyes running more than one AJAX request makes still no sense. The only benefit I see is that files included in the page (i.e. CSS, JavaScript,…) are downloaded faster as they can downloaded at the same time. Another thing that will be better are mouseover events that change images while an AJAX request is running.
Internet Explorer 8 includes two new read-only properties of the window object that enable your server to determine the number of available connections on the client computer: window.maxConnectionsPerServer (http 1.1) andwindow.maxConnectionsPer1_0Server (http 1.0).
Read more details at Connectivity Enhancements in Internet Explorer 8 (MSDN), IE8: The Performance Implications, Testing IE8’s Connection Parallelism, IE8: Better Ajax, CSS, DOM, and new features.
Update: there is another new property, the XMLHttpRequest’s timeout. With the timeout property, Web developers can specify the length of time in milliseconds for the host to wait for a response before timing out the connection. I’m very sure that this new property and the event timeoutRaised will be added by the Firefox developers very soon.
Update 2: Updated the citation to include the recommendation that a single-user client SHOULD NOT maintain more than two connections. Well, it was defined in 1999 and Web has changed since then but I still would like to see Web applications only accessing my Web server with one connection. The only reason to have more than one connection: downloading files (CSS, JavaScript, or in common big files that are saved to disk). In the documentation of connectivity enhancements in IE8the registry key FEATURE_AJAX_CONNECTIONSERVICES will set the new maximum number back to two concurrent connections. I don’t know why there is the name AJAX used. ASP.NET developers may get in trouble if they are using the Session object and running concurrent AJAX requests as each requests has to wait until the previous has been finished.
Published Monday, July 21, 2008 3:42 PM by Michael Schwarz

Firefox / IE Browser Tweaks

2005.10.04 07:56 EST by Philip

Below, you will find browser-specific settings and registry entries to speed up both Firefox and Internet Explorer. The settings are generally intended for broadband internet connections, and can noticeably improve your web browsing experience.

Internet Explorer

According to the HTTP specs, only a limited number of simultaneous connections to web servers are allowed, while loading web pages. With today's broadband connections, it is beneficial to increase the number of concurrent connections to reduce page loading time. To increase the number of concurrent connections, add the following entries to the Windows Registry (the settings are not present by default):

Navigate to Start > Run, type: regedit , find the following locations and add the DWORD values:

HKEY_USERS.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings
"MaxConnectionsPerServer"=dword:00000010
"MaxConnectionsPer1_0Server"=dword:00000010

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings
"MaxConnectionsPerServer"=dword:00000010
"MaxConnectionsPer1_0Server"=dword:00000010

Notes: Keep in mind that setting those values exceed the HTTP RFC specs. Increasing the number of concurrent connections over 10 may cause problems with some websites not completely loading, or dropping/retransmitting some requests. If you experience problems, just reduce the numbers to a lower value, or remove the settings above to return to the Windows defaults (4 and 2 concurrent connections).

The above parameters, and the web patch in the downloads section of the site work with Internet Explorer versions 4 and above.

Alternatively, to apply the above tweak, you can download a web patch (sguide_webtweak_2k) from the download section of the website.

While these entries improve web page loading considerably, there is some concern that they tend to strain webservers more (they increase bursts of concurrent requests), but have no effect on average throughput.

References: Q183110 - "WinInet Limits IE connections per server".

Firefox

Pipelining requests

This setting is equivalent to the IE tweak above. It allows for more simultaneous connections to web servers. Note that the HTTP specs suggest for 4 concurrent connections. Setting this value to 10 allows for more web page components being downloaded at the same time, noticeably improving browsing. To appy the tweak, follow the simple instructions below:

1. In the address bar, type: about:config
2. Locate and change the following values (by double-clicking on them):
network.http.max-connections = 24 (default is 24)
network.http.max-connections-per-server = 10 (default is 8)
network.http.max-persistent-connections-per-proxy = 8 (default is 4)
network.http.max-persistent-connections-per-server = 4 (default is 2)
network.http.pipelining = true (default is false)
network.http.pipelining.maxrequests = 10 ( default is 4)
network.http.proxy.pipelining = true (default is false)
3. Optionally, you can also tweak the following settings:
content.notify.backoffcount = 5
ui.submenuDelay = 0

Note: Setting the number of connections per server to a much higher number (over ~10) can cause web servers to drop some requests, resulting in incomplete pages, increased retransmissions, etc., so it is not recommended.

Reduce Initial Page Delay

By default, Firefox waits 0.25 seconds (250ms) before beginning to draw web pages. To reduce this initial delay, do the following:

1. In the browser address bar, type: about:config
2. Anywhere in the browser window, right-click and create: NEW > String
3. Name the string: nglayout.initialpaint.delay (no spaces) and set its value to 0 (or something sensible, in milliseconds).

Note: This setting is not present by default.

Advanced Firefox Settings

Below, you will find settings that may increase your perceived page loading time a bit further. Note that those are most likely best left at the default values. These settings generally do no exist under the Firefox about:config, and need to be created if you'd like to experiment with them.

content.interrupt.parsing - default/recommended is true. When true, parsing can be interrupted to process UI events.
content.max.tokenizing.time recommended value ~ 2250000. Defines maximum number of microseconds between reflows.
content.notify.interval - recommended value ~ 750000
content.notify.ontimer - recommended set to true. If so, doesn't reflow pages more often than the content.notify.interva timer.
content.switch.threshold - raising the value will make the browser more responsive at the expense of page load time.
browser.cache.memory.capacity - memory, in KB reserved for caching decoded images. Default varies with RAM

Google Chrome Navigator UserAgent String

2008-09-02T16:36:00.000-07:00

Here is the Google Chrome navigator.userAgent string.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13

Beware that it is very similar to Apple's Safari string and would be identified as Safari by legacy code. Modify your code to match.

Tuning Windows Server 2003 on IBM

2008-08-21T13:42:00.000-07:00

http://www.redbooks.ibm.com/redpapers/pdfs/redp3943.pdf

Error logging in HTTP API

2008-08-21T11:04:00.000-07:00

Hacker Attack from Turkey - Blocked by IIS

2008-08-21 15:47:13 89.106.8.2 2573 192.168.0.40 80 HTTP/1.1 GET /w00tw00t.at.ISC.SANS.DFind:) 400 - Hostname -

Browser Failing to Close Connection - Safari/Firefox - FYI

2008-08-21 17:14:51 69.107.57.53 53347 192.168.0.40 80 - - - - - Timer_ConnectionIdle -

Congested Connection - Request Failed

2008-08-15 06:05:18 58.253.81.211 1665 192.168.0.40 80 - - - - - Timer_MinBytesPerSecond -

400 Error - File Request Failed

2008-08-18 14:16:57 59.93.122.145 2431 192.168.0.40 80 HTTP/1.1 GET /ad/Uploads/editor/"%20+url%20+" 400 - URL -

IIS 6.0 Documentation > IIS 6.0 Technical Reference > Troubleshooting IIS 6.0 > HTTP Status Codes in IIS 6.0

Other HTTP.sys Error Log Errors (IIS 6.0)

In some cases, HTTP.sys generates entries in its error log that are not associated with a specific HTTP request and that do not have HTTP error codes. Table 11.12 Other HTTP.sys Errors lists these errors.
Table 11.12 Other HTTP.sys Errors
Logged Reason Code Condition
Timer_ConnectionIdle
The connection was reset as its idle time exceeded the ConnectionTimeout property.
Timer_HeaderWait
The headers for the request were not received within the time limit specified by the HeaderWaitTimeout property.
Timer_MinBytesPerSecond
The throughput rate of this connection has dropped below the limit specified in the MinFileBytesPerSec property.
Timer_EntityBody
The entity body was not received within the specified timeout.
Timer_Response
The connection was reset because the response was not processed within the specified time limit.
Timer_AppPool
The connection was reset because the request stayed in the request queue of the application pool longer than the specified time limit.
For complete information about the errors logged in the HTTP error log, see Error Logging in the HTTP API. For more information about available configuration options in HTTP.sys, see Microsoft Knowledge Base article 820129, Inf: Http.sys Registry Settings for IIS.

Table 11.12 Other HTTP.sys Errors
Timer_ConnectionIdle	The connection was reset as its idle time exceeded the ConnectionTimeout property.
Timer_HeaderWait	The headers for the request were not received within the time limit specified by the HeaderWaitTimeout property.
Timer_MinBytesPerSecond	The throughput rate of this connection has dropped below the limit specified in the MinFileBytesPerSec property.
Timer_EntityBody	The entity body was not received within the specified timeout.
Timer_Response	The connection was reset because the response was not processed within the specified time limit.
Timer_AppPool	The connection was reset because the request stayed in the request queue of the application pool longer than the specified time limit.

Error logging in HTTP API

View products that this article applies to.
Article ID : 820729
Last Review : March 14, 2008
Revision : 7.0
On This Page
SUMMARY
MORE INFORMATION
Configure HTTP API error logging
Format of the HTTP API error logs
Types of errors that the HTTP API logs
REFERENCES
SUMMARY
This article describes the error logging capabilities of Hypertext Transfer Protocol (HTTP) APIs.

Some errors that occur in an HTTP-based application are automatically handled by the HTTP API instead of being passed back to an application for handling. This behavior occurs because the frequency of such errors might otherwise flood an event log or an application handler.

The following topics describe the different aspects of HTTP API error logging:
• Configure HTTP API error logging
Registry settings control the HTTP API logs errors, the maximum permitted size of log files, and the location of the log files.
• Format of the HTTP API error logs
The HTTP API creates log files that comply with the World Wide Web Consortium (W3C) log file conventions. You can use standard tools to parse these log files. However, unlike W3C log files, HTTP API log files do not contain the columns names.
• Types of errors that the HTTP API logs
The HTTP API logs a variety of common errors.
Back to the top
MORE INFORMATION
Configure HTTP API error logging
Three registry values under an HTTP \Parameters key control the HTTP API error logging. These keys are located at the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Note The location and the form of the configuration values may change in later versions of the Microsoft Windows operating system.

You must have Administrator/Local System credentials to change the registry values, and to view or modify the log files and the folder that contains them.

Configuration information in the registry values is read when the HTTP API driver starts. Therefore, if you change the settings, you must stop, and then restart the driver to read the new values. To do this, type the following console commands:
net stop http
net start http
The following naming convention is used to name the log files:
httperr + sequence number + .log
Example: httperr4.log
Log files are cycled when they reach the maximum size that the ErrorLogFileTruncateSize registry value specifies. This value cannot be less than one megabyte (MB).

If the configuration of error logging is not valid, or if any type of failure occurs while the HTTP API is writing to the log files, the HTTP API uses event logging to notify administrators that error logging is not occurring.

The following table describes the registry configuration values.
Registry value Description
EnableErrorLogging A DWORD that you can set to TRUE to enable error logging or to FALSE to disable it. The default value is TRUE.
ErrorLogFileTruncateSize A DWORD that specifies the maximum size of an error log file, in bytes. The default value is one MB (0x100000).

Note The specified value cannot be smaller than the default value.
ErrorLoggingDir A String that specifies the folder where the HTTP API puts its logging files.

The HTTP API creates a subfolder HTTPERR in the specified folder, and then stores the log files in the subfolder. This subfolder and the log files receive the same permission settings. The Administrator and Local System Accounts have full access. Other users do not have access.

The following is the default folder when the folder is not specified in the registry:
%SystemRoot%\System32\LogFiles

Note The ErrorLoggingDir string value must be a fully qualified path. However, it can contain %SystemRoot%.

Back to the top
Format of the HTTP API error logs
Generally, HTTP API error log files have the same format as W3C error logs, except that HTTP API error log files do not contain column headings. Each line of an HTTP API error log records one error. The fields appear in a specific order. A single space character (0x0020) separates each field from the previous field. In each field, plus signs (0x002B) replace space characters, tabs, and nonprintable control characters.

The following table identifies the fields and the order of the fields in an error log record.
Field Description
Date The Date field follows the W3C format. This field is based on Coordinated Universal Time (UTC). The Date field is always ten characters in the form of YYYY-MM-DD. For example, May 1, 2003 is expressed as 2003-05-01.
Time The Time field follows the W3C format. This field is based on UTC. The time field is always eight characters in the form of MM:HH:SS. For example, 5:30 PM (UTC) is expressed as 17:30:00.
Client IP Address The IP address of the affected client. The value in this field can be either an IPv4 address or an IPv6 address. If the client IP address is an IPv6 address, the ScopeId field is also included in the address.
Client Port The port number for the affected client.
Server IP Address The IP address of the affected server. The value in this field can be either an IPv4 address or an IPv6 address. If the server IP address is an IPv6 address, the ScopeId field is also included in the address.
Server Port The port number of the affected server.
Protocol Version The version of the protocol that is being used.

If the connection has not been parsed sufficiently to determine the protocol version, a hyphen (0x002D) is used as a placeholder for the empty field.

If either the major version number or the minor version number that is parsed is greater than or equal to 10, the version is logged as HTTP/?.?.
Verb The verb state that the last request that is parsed passes. Unknown verbs are included, but any verb that is more than 255 bytes is truncated to this length. If a verb is not available, a hyphen (0x002D) is used as a placeholder for the empty field.
CookedURL + Query The URL and any query that is associated with it are logged as one field that is separated by a question mark (0x3F). This field is truncated at its length limit of 4096 bytes.

If this URL has been parsed ("cooked"), it is logged with local code page conversion, and is treated as a Unicode field.

If this URL has not been parsed ("cooked") at the time of logging, it is copied exactly, without any Unicode conversion.

If the HTTP API cannot parse this URL, a hyphen (0x002D) is used as a placeholder for the empty field.
Protocol Status The protocol status cannot be greater than 999.

If the protocol status of the response to a request is available, it is logged in this field.

If the protocol status is not available, a hyphen (0x002D) is used as a placeholder for the empty field.
SiteId Not used in this version of the HTTP API. A placeholder hyphen (0x002D) always appears in this field.
Reason Phrase This field contains a string that identifies the type of error that is being logged. This field is never left empty.
Queue Name This the request queue name.
The following sample lines are from an HTTP API error log:
2002-07-05 18:45:09 172.31.77.6 2094 172.31.77.6 80 HTTP/1.1 GET /qos/1kbfile.txt 503 – ConnLimit 2002-07-05 19:51:59 127.0.0.1 2780 127.0.0.1 80 HTTP/1.1 GET /ThisIsMyUrl.htm 400 – Hostname 2002-07-05 19:53:00 127.0.0.1 2894 127.0.0.1 80 HTTP/2.0 GET / 505 - Version_N/S 2002-07-05 20:06:01 172.31.77.6 64388 127.0.0.1 80 - - - - - Timer_MinBytesPerSecond
Back to the top
Types of errors that the HTTP API logs
The HTTP API logs error responses to clients, connection time-outs, orphaned requests, and dropped connections that are handled incorrectly.

The following list identifies the types of errors that the HTTP API logs:
• Responses to clients The HTTP API sends an error response to a client, for example, a 400 error that is caused by a parse error in the last received request. After the HTTP API sends the error response, it terminates the connection.
• Connection time-outs The HTTP API times out a connection. If a request is pending when the connection times out, the request is used to provide more information about the connection in the error log.
• Orphaned requests A user-mode process quits unexpectedly while there are still queued requests that are routed to that process. The HTTP API logs the orphaned requests in the error log.
Specific error types are designated by Reason Phrase strings that always appear as the last field of each error line. The following table identifies the HTTP API Reason Phrases.
Reason Phrase Description

AppOffline A service unavailable error occurred (an HTTP error 503). The service is not available because application errors caused the application to be taken offline.
AppPoolTimer A service unavailable error occurred (an HTTP error 503). The service is not available because the application pool process is too busy to handle the request.
AppShutdown A service unavailable error occurred (an HTTP error 503). The service is not available because the application shut down automatically in response to administrator policy.
BadRequest A parse error occurred while processing a request.
Connection_Abandoned_By_AppPool A worker process from the application pool that quit unexpectedly or orphaned a pending request by closing its handle.
Connection_Dropped The connection between the client and the server was closed before the server could send its final response packet. The most common cause of this behavior is that the client prematurely closes its connection to the server.
ConnLimit A service unavailable error occurred (an HTTP error 503). The service is not available because the site level connection limit has been reached or exceeded.
Connections_Refused The kernel NonPagedPool memory has dropped below 20MB and http.sys has stopped receiving new connections
Disabled A service unavailable error occurred (an HTTP error 503). The service is not available because an administrator has taken the application offline.
EntityTooLarge An entity exceeded the maximum size that is permitted.
FieldLength A field length limit was exceeded.
Forbidden A forbidden element or sequence was encountered while parsing.
Header A parse error occurred in a header.
Hostname A parse error occurred while processing a Hostname.
Internal An internal server error occurred (an HTTP error 500).
Invalid_CR/LF An illegal carriage return or line feed occurred.
LengthRequired A required length value was missing.
N/A A service unavailable error occurred (an HTTP error 503). The service is not available because an internal error (such as a memory allocation failure) occurred.
N/I A not-implemented error occurred (an HTTP error 501), or a service unavailable error occurred (an HTTP error 503) because of an unknown transfer encoding.
Number A parse error occurred while processing a number.
Precondition A required precondition was missing.
QueueFull A service unavailable error occurred (an HTTP error 503). The service is not available because the application request queue is full.
RequestLength A request length limit was exceeded.
Timer_AppPool The connection expired because a request waited too long in an application pool queue for a server application to dequeue and process it. This timeout duration isConnectionTimeout. By default, this value is set to two minutes.
Timer_ConnectionIdle The connection expired and remains idle. The default ConnectionTimeout duration is two minutes.
Timer_EntityBody The connection expired before the request entity body arrived. When it is clear that a request has an entity body, the HTTP API turns on the Timer_EntityBody timer. Initially, the limit of this timer is set to the ConnectionTimeout value (typically 2 minutes). Each time another data indication is received on this request, the HTTP API resets the timer to give the connection two more minutes (or whatever is specified in ConnectionTimeout).
Timer_HeaderWait The connection expired because the header parsing for a request took more time than the default limit of two minutes.
Timer_MinBytesPerSecond The connection expired because the client was not receiving a response at a reasonable speed. The response send rate was slower than the default of 240 bytes/sec.
Timer_Response Reserved. Not currently used.
URL A parse error occurred while processing a URL.
URL_Length A URL exceeded the maximum permitted size.
Verb A parse error occurred while processing a verb.
Version_N/S A version-not-supported error occurred (an HTTP error 505).

Back to the top
REFERENCES
For more information about adding additional logging fields for IIS HTTP error logging, click the following article number to view the article in the Microsoft Knowledge Base:
832975 Additional properties are now available for logging in the Httperr#.log file in IIS 6.0 and IIS 7.0
Back to the top
APPLIES TO
• Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
• Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
• Microsoft Windows Server 2003, Standard Edition (32-bit x86)
• Microsoft Windows Server 2003, Web Edition
• Microsoft Windows Small Business Server 2003 Premium Edition
• Microsoft Windows Small Business Server 2003 Standard Edition

Javascript Tips

2008-08-20T14:00:00.000-07:00

Tips\JavaScript

Format Time
Format Date
Round to 0 or .5
Days Between Dates
Repeat String
Printer Friendly Pages
Fill In Blank Table Cells
Is Valid Time
Custom No Documents Found Message
Selecting check box highlights entire row
Time Zones
Order Of Execution
Number Of Weekdays Between Dates
JavaScript Sorting
parseInt Bug
isArray Function
Move Up/Down List
Add To List/Remove From List
JavaScript Are Arrays Equal
Show Object Properties
Open Centered Window
Capturing Mouse Position
String Manipulations
Checking For Global Variables
Generic Form Validation
Get Field Value
Trim String
Replace Substring Function
Get Selected Radio Button Or Check Box
Using Pages To Store JavaScript
Validating A Date String
Capturing Keystrokes

Safari 3: “The fastest web browser on any platform”?

2008-08-20T11:46:00.000-07:00

“The fastest web browser on any platform”?

According to Steve Jobs Safari is the fastest browser on Windows. Now he isn't very clear on the exact definition of "fastest", and as Apple CEO he'll have a rather hard time avoiding charges of prejudice in any case.
During @media 2007 Europe it was very fashionable to complain about Safari's lack of speed (to be fair: we were talking about 2, not 3). The consensus seemed to be that Safari may be pretty quick in loading web pages, but it can be agonizingly slow in closing down web pages, especially those that have plugin content. Jobs didn't mention these problems in his keynote.
Then I went through my DOM vs. innerHTML and style vs. classNamebenchmarks in Safari Windows, and the test results are pretty awesome. So awesome, in fact, that I started to suspect there's something wrong.
Fortunately, for once I didn't have to do the dirty work myself. Mark "Tarquin" Wilton-Jones did some extensive testing and found the cause:
Safari does not update the date objects correctly. It appears to pause the date object while iframe src changing, page loading, and parsing is taking place, so the next request for a date object produces one with the same time as the one in the parent page. Even when forcing it not to cache the page, this still happens (and yes, I tested many times since I did not believe it myself). The page load itself could be seen to take about half of a second when timed with a stopwatch. Clearly, Safari has a bug with date objects here.
(And yes, this is the actual sequence of events: first I started to doubt Safari's reported benchmark results, and only a few hours later I read Mark's article.)
It gets worse, though. During his keynote, Jobs showed IE7 and Safari Windows running side by side, and noted the speed with which the browsers downloaded and displayed a few key test pages. Guess whih browser was fastest? Hint: it wasn't the one from the giant Apple competitor.
Obviously, any such speed test must use the load event: show load time when the page has been loaded completely. Unfortunately the load event in Safari is different from the same event in other browsers. Mark explains:
Safari does not fire onload at the same time as other browsers. With most browsers, they will wait until the page is loaded, all images and stylesheets and scripts have run, and the page has been displayed before they fire onload. Safari does not.
In Safari, it seems onload fires before the page has been displayed, before layout has been calculated, before any costly reflows have taken place. It fires before images have completed decoding (this can also happen in rare cases in Opera, but Safari seems to do it everywhere), meaning that a substantial part of the load time is not included. So basically, onload is not trustworthy in Safari for checking page loading times.
So Jobs' speed testing is unreliable. It compares Safari's load event to IE's, and the two are different. From a propaganda point of view Jobs said and showed the right thing, but from a technical point of view it's completely worthless.
The "fastest browser on any platform" claim is based on faulty implementations of the Date object and the load event, and is therefore untrustworthy.
Until these problems are solved we cannot really compare Safari's speed to other browsers' speed; and we must perforce conclude that Apple's test results are (let's keep this nice) too flattering.

Javascript References - Gecko, Webkit, Explorer

2008-08-09T13:42:00.000-07:00

Here are the starting points for exploring Javascript. Explorer @ MSDN, Gecko @ Mozilla/Firefox, and Webkit used in Apple's Safari and Google's Android platforms.

HTML and DHTML Reference (Internet Explorer @ MSDN)

This section contains reference information for the Dynamic HTML (DHTML) API.
Dynamic HTML (DHTML) Object Model References
DHTML Collections
This section contains a list of the collections exposed by the DHTML Object Model.
DHTML Constants
This section lists the constants in the DHTML Object Model.
DHTML Events
This section contains the events exposed by the DHTML Object Model.
DHTML Methods
This section contains a list of the methods exposed by the DHTML Object Model.
DHTML Objects
This section contains a list of the objects defined by DHTML.
DHTML Properties
This section contains a list of the properties in the DHTML Object Model.
HTML References
HTML Character Sets
Character sets determine how the bytes that represent the text of your HTML document are translated to readable characters. Windows Internet Explorer interprets the bytes in your document according to the applied character set translations.
HTML Elements
This section contains a list of elements defined by HTML. The links take you to the element definitions, which contain the set of members for the element.
Cascading Style Sheets (CSS) References
CSS Attributes: Index
This index lists all the supported Cascading Style Sheets (CSS) attributes by category, and indicates the version of Internet Explorer in which the attributes were first available.
CSS Length Units Reference
This section defines the supported length units for CSS
Additional References
Color Table
Colors can be specified in HTML pages in two ways
Command Identifiers
Command identifiers specify an action to take on the given object.
Default Behaviors Reference
Introduction to DHTML Behaviors provides a means for Web developers to extend the current Internet Explorer object model. A number of behaviors have been implemented as part of Microsoft Internet Explorer 5 and are referred to as default behaviors.
Language Codes
The following table lists all the possible language codes used to specify various system settings.
Tips and Tricks
As with any type of programming, writing bug-free, efficient scripts that meet your expectations takes a bit of work. The following sections provide some tips and hints to make that work take less time and go more smoothly.
Visual Filters and Transitions Reference
As of Internet Explorer 4.0, you can apply multimedia-style effects to your Web pages using visual filters and transitions. You can apply visual filters and transitions to standard HTML controls, such as text containers, images, and other windowless objects. Transitions are time-varying filters that create a transition from one visual state to another. By combining filters and transitions with basic scripting, you can create visually engaging and interactive documents.

Gecko DOM Reference

This is the table of contents for the Gecko DOM reference.
Preface
About This Reference
Who Should Read This Guide
What is Gecko?
API Syntax
Using the Examples
Introduction
What is the DOM?
DOM and JavaScript
How Do I Access the DOM?
Important Data Types
DOM Interfaces
Testing the DOM API
[edit]DOM element Reference
Introduction
Properties
Methods
Event Handlers
[edit]DOM window Reference
Introduction
Properties
Methods
Event Handlers
[edit]DOM document Reference
Introduction
Properties
Methods
Event Handlers
[edit]DOM event Reference
Introduction
Properties
Methods
[edit]DOM style Reference
Notes
Material to be moved to other pages
[edit]DOM range Reference
Introduction
Properties
Methods
[edit]DOM selection Reference
Introduction
Glossary
Properties
Methods
See Also
External links
[edit]DOM - Other Objects
Attr
CDATASection
CharacterData
Comment
DocumentFragment
DocumentType
DOMConfiguration
DOMError
DOMErrorHandler
DOMException
DOMImplementation
DOMImplementationList
DOMImplementationRegistry
DOMImplementationSource
DOMLocator
DOMObject
DOMString
DOMStringList
DOMUserData
Entity
EntityReference
NameList
NamedNodeMap
Node
NodeList
Notation
ProcessingInstruction
Text
TypoInfo
UserDataHandler
[edit]HTML Form Element Interface
HTML Form Element Interface
Properties
Methods
[edit]HTML Table Element Interface
HTML Table Element Interface
Properties
Methods
[edit]HTML Table Row Element Interface
HTML Row Element Interface
Properties
Methods
[edit]DOM Examples
Example 1: height and width
Example 2: Image Attributes
Example 3: Manipulating Styles
Example 4: Using Stylesheets
Example 5: Event Propagation
Example 6: getComputedStyle
Example 7: Displaying Event Object Properties
Example 8: Using the DOM Table Interface

Core JavaScript Reference

WebReference.com

This book is a reference manual for the core JavaScript language for version 1.5. JavaScript is Netscape's cross-platform, object-based scripting language. Core JavaScript can be extended for a variety of purposes by supplementing it with additional objects.
About this Book
New Features in this Release
What You Should Already Know
JavaScript Versions
Where to Find JavaScript Information
Document Conventions

Part 1
Chapter 1 Objects, Methods, and Properties
Array
Boolean
Date
Function
java
JavaArray
JavaClass
JavaObject
JavaPackage
Math
netscape
Number
Object
Packages
RegExp
String
sun
Chapter 2 Top-Level Properties and Functions
decodeURI
decodeURIComponent
encodeURI
encodeURIComponent
eval
Infinity
isFinite
isNaN
NaN
Number
parseFloat
parseInt
String
undefined

Part 2
Chapter 3 Statements
break
const
continue
do...while
export
for
for...in
function
if...else
import
label
return
switch
throw
try...catch
var
while
with
Chapter 4 Comments
comment
Chapter 5 Operators
Assignment Operators
Comparison Operators
Using the Equality Operators
Arithmetic Operators
% (Modulus)
++ (Increment)
-- (Decrement)
- (Unary Negation)
Bitwise Operators
Bitwise Logical Operators
Bitwise Shift Operators
Logical Operators
String Operators
Special Operators
?: (Conditional operator)
, (Comma operator)
delete
function
in
instanceof
new
this
typeof
void

Part 3 LiveConn
Chapter 6 Java Classes, Constructors, and Methods
JSException
JSObject

Part 4
Appendix A Reserved Words
Appendix B Deprecated Features
Index

Safari CSS Reference (HTML) (PDF) Describes the Cascading Style Sheet (CSS) properties that are supported by Safari and the Web Kit.	2008-06-09
Safari HTML Reference (HTML) (PDF) Describes the Hypertext Markup Language (HTML) tags and properties that are supported by Safari and the Web Kit.	2008-01-15
Web Kit DOM Reference (HTML) Describes the API for accessing the Web Kit's Document Object Model.	2008-01-15
Apple Applications Schema Reference (HTML) (PDF) Describes the schemas used by Apple Applications to sync records such as contacts, calendars, and bookmarks.	2007-10-31
Sync Services Framework Reference (HTML) (PDF) Describes the Objective-C API for the Sync Services framework used to sync applications and devices.

Safari Javascript Events

2008-08-08T14:31:00.000-07:00

Apple Developer Support

Events make the client-side JavaScript world go ‘round. After a Web page loads, the only way a script can run is in response to a system or user action. While simple events have been part of the JavaScript vocabulary since the first scriptable browsers, more recent browsers implement robust event models that allow scripts to process events more intelligently. The problem, however, is that in order to support a wide range of browsers you must contend with multiple advanced event models. Three, to be exact.
The three event models align themselves with the Document Object Model (DOM) triumvirate: Netscape Navigator 4 (NN4), Internet Explorer 4 and later for Macintosh and Windows (IE4+), and the W3C DOM, as implemented in Safari. Despite sometimes substantial differences among the models, they can all work side-by-side in the same document with the help of a few JavaScript shortcuts. This article focuses on two key aspects of the conflicting event models:
Methods for binding an event to an HTML element object.
Processing the event after it fires.

One caveat about this approach: You cannot permit the statement to execute before the element’s tag loads in the browser. The reference to the button object is not valid until the HTML creates the element in the browser. Therefore, such binding statements need to run either at the bottom of the page or in a function invoked by theonLoad event handler of the BODY element.

W3C DOM Node Event Targets

The W3C DOM node architecture allows each node in a document tree to receive events. In browsers that support this architecture, event handlers assigned to text containers are not the targets of events that occur atop the nested text. The text nodes are the target objects. Consider the following:
In the events example, when the mouse pointer rolls atop the text of a SPAN element, the text within that span will be highlighted. Event binding occurs via object properties in the init() function. On the face of it, when a user rolls the mouse atop the SPAN element, the onMouseOver event action assigns the class name (highlight) associated with a style sheet rule that displays the text in bold face and a yellow background; with onMouseOut, the style reverts to its original version (class normal). Notice how one toggleHighlight() function performs both actions with the help of the event object’s type property (a property whose name is the same across all event model objects). Try the events example...

DOM events www.howtocreate.co.uk/tutorials/javascript/domevents

This is currently supported by Opera 7+, Mozilla/Firefox, Konqueror 3.0+, Safari, and NetFront 3.3+. It is also partially supported by iCab 3, ICEBrowser 5+, and Tkhtml Hv3. Espial claim that Escape/Evo 5 supports this, but it does not support even the basics.
Note: Internet Explorer on Windows does not comply with the standard here, so if you are testing, use a browser that supports the standard correctly, such as Opera. I will give details later on how to get support for Internet Explorer on Windows as well. Internet Explorer on Mac does not support either the DOM or IE events models.

Safari (web browser)

2008-07-11T18:32:00.000-07:00

Safari Developer FAQ
How do I detect the language setting for Safari?
What is the Safari user-agent string?
Does Safari support DHTML?
How do I determine methods for accessing objects?
How do I prevent my pages (and cookies) from being cached in Safari?
How do I test for cookies using JavaScript?
How do I add a Favicon (the small icon in the address bar)?
What version of Java does Safari use for running Applets?
How do I determine if Java is Available?
How does Safari handle server timeouts?
10. How does Safari handle server timeouts?
Safari on pre Mac OS X 10.3.6 systems will time out if it does not receive a response to an HTTP request or if server data transmission stops for 60 seconds. Safari on Mac OS X 10.3.6 and above effectively removes the 60 second limitation by setting the response timeout value to one year. That should be plenty of time for a server-side process to complete!
Back to Top
What type of plug-ins does Safari support?

Where should Safari plug-ins reside?
How do I ensure that my pages will work in Safari?
How do I debug JavaScript in Safari?
How do I report a Bug in Safari?
What CSS properties are supported in Safari?
Why are my Pop-Up Windows not appearing?
Does Safari support Live Connect?
Does Safari support XMLHttpRequest objects?
Does Safari support Tool-Tips?
Does Safari support XSLT?
How do I tell Safari I have an RSS feed?
Does Safari work with .NET and ASPX based sites?
Does Safari support Frames, Framesets and iFrames?
What's different about Safari running on an Intel-based Macintosh?

Mac OS X and Safari Browser’s Market Share at Record High

June 1, 2008

The Net Applications survey indicates that Apple’s share of the operating system market grew by a astonishing 5.69% in May to hit a record high of 7.83%. Apple’s Safari Web browsershare also hit new all-time high of 6.25% in May 2008.
Microsoft Windows OS, which still runs on 9 out of 10 computers on the Internet, fell half a point to a record low 91.17%. The iPhone’s OS, which is measured separately from Mac OS X, held 0.16% of US market share in May, compared to 0.14% in April...

From Wikipedia, the free encyclopedia

Safari

Safari 3 on Mac OS X 10.5 Leopard.
Developed by	Apple Inc.
Initial release	January 7, 2003
Stable release	3.1.2 (June 30, 2008; 42 days ago) _[+/−]
Preview release	4.0 Developer Beta (June 11, 2008; 61 days ago) _[+/−]
OS	Mac OS X Microsoft Windows iPhone OS
Development status	Current
Type	Web browser
License	Proprietary Engine under GNU LGPL
Website	apple.com/safari

Since the release of Safari, its usage share has been steadily climbing. According to Net Applications, Safari's marketshare for May 2008 was 6.25%.^[4]
Contents

1 Features
1.1 CSS support
2 History and development
3 Criticism
3.1 Distribution through Apple Software Update
3.2 PWN 2 OWN Browser Exploit
3.3 Microsoft security advisory
3.4 End-user license agreement
4 Version compatibility
5 Version history
5.1 Mac
5.2 Windows
5.3 Mobile
6 See also
7 References
8 External links

The Cross Browser Problem

2008-07-09T13:18:00.000-07:00

Explorer, Firefox, and Safari represent over 99% of the browsers used globally. Below are the global numbers.

Each browser version on each operating system behave differently. The challenge is to develop and test web applications that support every combination of browser and operating system. IE6, IE7, FF2, FF3, S3 on XP, Vista, Mac, iPhone, Linux define the modern 25 combinations that need to be supported.

Much of the information on the Internet is old, and not updated. Most blog posts refer to IE4, IE5, IE6, IE7, Navigator6, FF1, and FF2 on Windows 2000 and XP. The methods described too frequently have quirks when used with Macintosh browsers and platforms.

The share of Macintosh and iPhone users has been growing, representing possibly 15% of users in the United States. As Apple expands it's world-wide distribution, iPhone defines true web access via smartphones, and Google Android on Linux changes open phone access - support for modern platforms become more critical.

As we solve these problems, we'll be posting solutions on this blog.

Version	HTTP 1.0 server (broadband)	HTTP 1.1 server (broadband)	HTTP 1.0 server (narrowband)	HTTP 1.1 server (narrowband)
Internet Explorer 7 and earlier	4	2	4	2
Internet Explorer 8	6	6	4	2

Table 11.12 Other HTTP.sys Errors
Logged Reason Code	Condition
Timer_ConnectionIdle	The connection was reset as its idle time exceeded the ConnectionTimeout property.
Timer_HeaderWait	The headers for the request were not received within the time limit specified by the HeaderWaitTimeout property.
Timer_MinBytesPerSecond	The throughput rate of this connection has dropped below the limit specified in the MinFileBytesPerSec property.
Timer_EntityBody	The entity body was not received within the specified timeout.
Timer_Response	The connection was reset because the response was not processed within the specified time limit.
Timer_AppPool	The connection was reset because the request stayed in the request queue of the application pool longer than the specified time limit.

•	Configure HTTP API error logging Registry settings control the HTTP API logs errors, the maximum permitted size of log files, and the location of the log files.
•	Format of the HTTP API error logs The HTTP API creates log files that comply with the World Wide Web Consortium (W3C) log file conventions. You can use standard tools to parse these log files. However, unlike W3C log files, HTTP API log files do not contain the columns names.
•	Types of errors that the HTTP API logs The HTTP API logs a variety of common errors.

Registry value	Description
EnableErrorLogging	A DWORD that you can set to TRUE to enable error logging or to FALSE to disable it. The default value is TRUE.
ErrorLogFileTruncateSize	A DWORD that specifies the maximum size of an error log file, in bytes. The default value is one MB (0x100000). Note The specified value cannot be smaller than the default value.
ErrorLoggingDir	A String that specifies the folder where the HTTP API puts its logging files. The HTTP API creates a subfolder HTTPERR in the specified folder, and then stores the log files in the subfolder. This subfolder and the log files receive the same permission settings. The Administrator and Local System Accounts have full access. Other users do not have access. The following is the default folder when the folder is not specified in the registry: %SystemRoot%\System32\LogFiles Note The ErrorLoggingDir string value must be a fully qualified path. However, it can contain %SystemRoot%.

Field	Description
Date	The Date field follows the W3C format. This field is based on Coordinated Universal Time (UTC). The Date field is always ten characters in the form of YYYY-MM-DD. For example, May 1, 2003 is expressed as 2003-05-01.
Time	The Time field follows the W3C format. This field is based on UTC. The time field is always eight characters in the form of MM:HH:SS. For example, 5:30 PM (UTC) is expressed as 17:30:00.
Client IP Address	The IP address of the affected client. The value in this field can be either an IPv4 address or an IPv6 address. If the client IP address is an IPv6 address, the ScopeId field is also included in the address.
Client Port	The port number for the affected client.
Server IP Address	The IP address of the affected server. The value in this field can be either an IPv4 address or an IPv6 address. If the server IP address is an IPv6 address, the ScopeId field is also included in the address.
Server Port	The port number of the affected server.
Protocol Version	The version of the protocol that is being used. If the connection has not been parsed sufficiently to determine the protocol version, a hyphen (0x002D) is used as a placeholder for the empty field. If either the major version number or the minor version number that is parsed is greater than or equal to 10, the version is logged as HTTP/?.?.
Verb	The verb state that the last request that is parsed passes. Unknown verbs are included, but any verb that is more than 255 bytes is truncated to this length. If a verb is not available, a hyphen (0x002D) is used as a placeholder for the empty field.
CookedURL + Query	The URL and any query that is associated with it are logged as one field that is separated by a question mark (0x3F). This field is truncated at its length limit of 4096 bytes. If this URL has been parsed ("cooked"), it is logged with local code page conversion, and is treated as a Unicode field. If this URL has not been parsed ("cooked") at the time of logging, it is copied exactly, without any Unicode conversion. If the HTTP API cannot parse this URL, a hyphen (0x002D) is used as a placeholder for the empty field.
Protocol Status	The protocol status cannot be greater than 999. If the protocol status of the response to a request is available, it is logged in this field. If the protocol status is not available, a hyphen (0x002D) is used as a placeholder for the empty field.
SiteId	Not used in this version of the HTTP API. A placeholder hyphen (0x002D) always appears in this field.
Reason Phrase	This field contains a string that identifies the type of error that is being logged. This field is never left empty.
Queue Name	This the request queue name.

•	Responses to clients The HTTP API sends an error response to a client, for example, a 400 error that is caused by a parse error in the last received request. After the HTTP API sends the error response, it terminates the connection.
•	Connection time-outs The HTTP API times out a connection. If a request is pending when the connection times out, the request is used to provide more information about the connection in the error log.
•	Orphaned requests A user-mode process quits unexpectedly while there are still queued requests that are routed to that process. The HTTP API logs the orphaned requests in the error log.

Reason Phrase	Description
AppOffline	A service unavailable error occurred (an HTTP error 503). The service is not available because application errors caused the application to be taken offline.
AppPoolTimer	A service unavailable error occurred (an HTTP error 503). The service is not available because the application pool process is too busy to handle the request.
AppShutdown	A service unavailable error occurred (an HTTP error 503). The service is not available because the application shut down automatically in response to administrator policy.
BadRequest	A parse error occurred while processing a request.
Connection_Abandoned_By_AppPool	A worker process from the application pool that quit unexpectedly or orphaned a pending request by closing its handle.
Connection_Dropped	The connection between the client and the server was closed before the server could send its final response packet. The most common cause of this behavior is that the client prematurely closes its connection to the server.
ConnLimit	A service unavailable error occurred (an HTTP error 503). The service is not available because the site level connection limit has been reached or exceeded.
Connections_Refused	The kernel NonPagedPool memory has dropped below 20MB and http.sys has stopped receiving new connections
Disabled	A service unavailable error occurred (an HTTP error 503). The service is not available because an administrator has taken the application offline.
EntityTooLarge	An entity exceeded the maximum size that is permitted.
FieldLength	A field length limit was exceeded.
Forbidden	A forbidden element or sequence was encountered while parsing.
Header	A parse error occurred in a header.
Hostname	A parse error occurred while processing a Hostname.
Internal	An internal server error occurred (an HTTP error 500).
Invalid_CR/LF	An illegal carriage return or line feed occurred.
LengthRequired	A required length value was missing.
N/A	A service unavailable error occurred (an HTTP error 503). The service is not available because an internal error (such as a memory allocation failure) occurred.
N/I	A not-implemented error occurred (an HTTP error 501), or a service unavailable error occurred (an HTTP error 503) because of an unknown transfer encoding.
Number	A parse error occurred while processing a number.
Precondition	A required precondition was missing.
QueueFull	A service unavailable error occurred (an HTTP error 503). The service is not available because the application request queue is full.
RequestLength	A request length limit was exceeded.
Timer_AppPool	The connection expired because a request waited too long in an application pool queue for a server application to dequeue and process it. This timeout duration isConnectionTimeout. By default, this value is set to two minutes.
Timer_ConnectionIdle	The connection expired and remains idle. The default ConnectionTimeout duration is two minutes.
Timer_EntityBody	The connection expired before the request entity body arrived. When it is clear that a request has an entity body, the HTTP API turns on the Timer_EntityBody timer. Initially, the limit of this timer is set to the ConnectionTimeout value (typically 2 minutes). Each time another data indication is received on this request, the HTTP API resets the timer to give the connection two more minutes (or whatever is specified in ConnectionTimeout).
Timer_HeaderWait	The connection expired because the header parsing for a request took more time than the default limit of two minutes.
Timer_MinBytesPerSecond	The connection expired because the client was not receiving a response at a reasonable speed. The response send rate was slower than the default of 240 bytes/sec.
Timer_Response	Reserved. Not currently used.
URL	A parse error occurred while processing a URL.
URL_Length	A URL exceeded the maximum permitted size.
Verb	A parse error occurred while processing a verb.
Version_N/S	A version-not-supported error occurred (an HTTP error 505).

•	Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
•	Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
•	Microsoft Windows Server 2003, Standard Edition (32-bit x86)
•	Microsoft Windows Server 2003, Web Edition
•	Microsoft Windows Small Business Server 2003 Premium Edition
•	Microsoft Windows Small Business Server 2003 Standard Edition

One Javascript

Sponsors

Introducing Y!OS 1.0 - live today!

Google and Yahoo host third-party JavaScript libraries

Google to host a number of JavaScript libraries

HTTP Status Code Definitions

10 Status Code Definitions

10.1 Informational 1xx

10.1.1 100 Continue

10.1.2 101 Switching Protocols

10.2 Successful 2xx

10.2.1 200 OK

10.2.2 201 Created

10.2.3 202 Accepted

10.2.4 203 Non-Authoritative Information

10.2.5 204 No Content

10.2.6 205 Reset Content

10.2.7 206 Partial Content

10.3 Redirection 3xx

10.3.1 300 Multiple Choices

10.3.2 301 Moved Permanently

10.3.3 302 Found

10.3.4 303 See Other

10.3.5 304 Not Modified

10.3.6 305 Use Proxy

10.3.7 306 (Unused)

10.3.8 307 Temporary Redirect

10.4 Client Error 4xx

10.4.1 400 Bad Request

10.4.2 401 Unauthorized

10.4.3 402 Payment Required

10.4.4 403 Forbidden

10.4.5 404 Not Found

10.4.6 405 Method Not Allowed

10.4.7 406 Not Acceptable

10.4.8 407 Proxy Authentication Required

10.4.9 408 Request Timeout

10.4.10 409 Conflict

10.4.11 410 Gone

10.4.12 411 Length Required

10.4.13 412 Precondition Failed

10.4.14 413 Request Entity Too Large

10.4.15 414 Request-URI Too Long

10.4.16 415 Unsupported Media Type

10.4.17 416 Requested Range Not Satisfiable

10.4.18 417 Expectation Failed

10.5 Server Error 5xx

10.5.1 500 Internal Server Error

10.5.2 501 Not Implemented

10.5.3 502 Bad Gateway

10.5.4 503 Service Unavailable

10.5.5 504 Gateway Timeout

10.5.6 505 HTTP Version Not Supported

Internet Explorer 8 and Maximum Concurrent Connections

Internet Explorer 8 and Maximum Concurrent Connections

Google Chrome Navigator UserAgent String

Tuning Windows Server 2003 on IBM

Error logging in HTTP API

Other HTTP.sys Error Log Errors (IIS 6.0)

Error logging in HTTP API

On This Page

SUMMARY

MORE INFORMATION

Configure HTTP API error logging

Format of the HTTP API error logs

Types of errors that the HTTP API logs

REFERENCES

APPLIES TO

Javascript Tips

Safari 3: “The fastest web browser on any platform”?

“The fastest web browser on any platform”?

Javascript References - Gecko, Webkit, Explorer

HTML and DHTML Reference (Internet Explorer @ MSDN)

Dynamic HTML (DHTML) Object Model References

HTML References

Cascading Style Sheets (CSS) References

Additional References

Gecko DOM Reference

Preface

Introduction