Common web browser errors

List of Web Application errors:

404 Not Found: The browser could not find the specific document that you requested on the host computer. To resolve this error, check the Uniform Resource Locator (URL) syntax (some URLs are case sensitive). In addition, the page may have been removed, had its name changed, or have been moved to a new location. To rise above the mundane, some have made 404 error pages a work of art – see 404 Research Lab for some creative 404 pages.

403 Forbidden/Access Denied: The Web site you requested requires special access permission (for example a password).

503 Service Unavailable: The host computer is too busy or the Web server which hosts the requested Web site is down.

Bad File Request: The form or the Hypertext Markup Language (HTML) code for an online form has an error.

Cannot Connect to Server: This error can occur if you are using Secure Sockets Layer (SSL) security (“https” at the beginning of the URL) when you are connecting to certain Web servers.

Cannot Add Form Submission Result to Bookmark List: The results of a form cannot be saved as a bookmark. A bookmark must be a document or a web address.

Cipher Strength value is 0-bit: When you click About Internet Explorer on the Help menu, the Cipher Strength value is 0-bit -and- you cannot connect to and view Web pages on secure Web sites can occur if the Schannel.dll, Rsabase.dll, or Rsaenh.dll files are missing, damaged, or of the incorrect version. See MSKB Q261328 for the fix.

Connection Reset by Peer: This message indicates that you clicked the “Stop” button or moved on to another webpage before the server finished sending the data/page.

Connection Refused by Host: This is a version of the 403 error. The Web site you requested requires special access permission. Or this page/site requires you to have SSL functionality not found in older browsers.

Error Copying File: Cannot copy file: File system error (1026): This message indicates that the Temporary Internet Files folder is full. Internet Explorer downloads files to the Temporary Internet Files Folder and then copies the files to the specified location. To resolve, go to the Tools menu in Internet Explorer and select Internet Options. On the General tab, click the Delete Files button in the ‘Temporary Internet Files’ section. If you would like to delete content that has been stored locally, select the ‘Delete all offline / subscription content’ check box. Click OK and click OK again.

Failed DNS Lookup: The Web site’s URL could not be translated into a valid Internet protocol (IP) address. This error is common on commercial sites because the computers responsible for translating the IP addresses are overloaded. Try again later when there may be less Internet traffic. This can also be caused by a URL syntax error (the URL has incorrect format).

File Contains no Data: The browser found the site, but nothing in the specific file. Try adding “:80” (without the quotation marks) to the URL just before the first slash, for example: http://www.microsoft.com:80/.

Helper Application not Found: You have attempted to download a file that needs a helper program and your browser cannot find the program. On the browser’s preferences or options menu, make sure the correct directory and file name are entered for the helper program. If you do not have a helper program, save the file to disk and obtain the helper program.

HTTP Server at Compressed .com:8080 Replies:HTTP/1.0 500 Error from Proxy: This error is common with proxy servers (a server on a local area network that lets you connect to the Internet without using a modem). The proxy is either down, busy, or cannot interpret the command that was sent to it. You may want to wait for 30 seconds or more then try viewing the page again. If the problem persists, contact the network administrator of that proxy.

NTTP Server Error: The browser could not find the Usenet newsgroup that you tried to access. Make sure the news server address is correctly listed in your browser’s preferences or options menu and try again.

Not Found: The link no longer exists.

Site Unavailable: Too many users are trying to access the site, the site is down for maintenance, there is noise on the line, or the site no longer exists. This can also be caused by a user URL syntax error.

TCP Error Encountered While Sending Request to Server: This error is caused by erroneous data on the line between you and the requested site. This may be hardware related. Report the error to your network administrator and try again later.

Unable to Locate Host: The URL did not return anything, the site is unavailable, or the Internet connection was dropped. Check the hardware connections and URL syntax.

Cannot Connect to Server: This error can occur if you are using Secure Sockets Layer (SSL) security (“https” at the beginning of the URL) when you are connecting to certain Web servers.

400: Bad Request: – The 400 Bad Request browser error means that the request you sent to the website server (i.e. a request to load a web page) was somehow malformed therefore the server was unable to understand or process the request.

401: Unauthorized: – The 401 Unauthorized browser error means the page you were trying to access can not be loaded until you first log on with a valid user ID and password. If you have just logged on and received the 401 Unauthorized error, it means that the credentials you entered were invalid. Invalid credentials could mean that you don’t have an account with the web site, your user ID was entered incorrectly, or you password was incorrect.

408: Request Timeout: – The 408 Request Timeout browser error means the request you sent to the website server (i.e. a request to load a web page) took longer than the website’s server was prepared to wait. In other words, your connection with the web site “timed out”.

500: Internal Server Error: – The 500 Internal Server Error is a very general browser error meaning something has gone wrong on the web site’s server but the server could not be more specific on what the exact problem is.

502: Bad Gateway: – The 502 Bad Gateway browser error means that one server received an invalid response from another server that it was accessing while attempting to load the web page or fill another request by the browser.

504: Gateway Timeout: – The 504 Gateway Timeout browser error means that one server did not receive a timely response from another server that it was accessing while attempting to load the web page or fill another request by the browser. This usually means that the other server is down or not working properly.

Source: Internet

Website Testing Checklist

Website Testing Checklist

1.1  LINKS

1.1.1 Check that the link takes you to the page it said it would.
1.1.2 Ensure to have no orphan pages (a page that has no links to it)
1.1.3 Check all of your links to other websites
1.1.4 Are all referenced web sites or email addresses hyperlinked?
1.1.5 If we have removed some of the pages from our own site, set up a custom 404 page that redirects your visitors to your home page (or a search page) when the user try to access a page that no longer exists.
1.1.6 Check all mailto links and whether it reaches properly

1.2 FORMS

1.2.1 Acceptance of invalid input
1.2.2 Optional versus mandatory fields
1.2.3 Input longer than field allows
1.2.4 Radio buttons
1.2.5 Default values on page load/reload(Also terms and conditions should be disabled)
1.2.6 Is Command Button can be used for HyperLinks and Continue Links ?
1.2.6 Is all the datas inside combo/list box are arranged in chronolgical order?
1.2.7 Are all of the parts of a table or form present? Correctly laid out? Can you confirm that selected texts are in the “right place?
1.2.8 Does a scrollbar appear if required?

1.3  DATA VERIFICATION AND VALIDATION

1.3.1 Is the Privacy Policy clearly defined and available for user access?
1.3.2 At no point of time the system should behave awkwardly when an invalid data is fed
1.3.3 Check to see what happens if a user deletes cookies while in site
1.3.4 Check to see what happens if a user deletes cookies after visiting a site
2. APPLICATION SPECIFIC FUNCTIONAL REQUIREMENTS

2.1 DATA INTEGRATION

2.1.1 Check the maximum field lengths to ensure that there are no truncated characters?
2.1.2 If numeric fields accept negative values can these be stored correctly on the database and does it make sense for the field to accept negative numbers?
2.1.3 If a particular set of data is saved to the database check that each value gets saved fully to the database. (i.e.) Beware of truncation (of strings) and rounding of numeric values.

2.2 DATE FIELD CHECKS

2.2.1 Assure that leap years are validated correctly & do not cause errors/miscalculations.
2.2.2 Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations.
2.2.3 Is copyright for all the sites includes Yahoo co-branded sites are updated

2.3 NUMERIC FIELDS

2.3.1 Assure that lowest and highest values are handled correctly.
2.3.2 Assure that numeric fields with a blank in position 1 are processed or reported as an error.
2.3.3 Assure that fields with a blank in the last position are processed or reported as an error an error.
2.3.4 Assure that both + and – values are correctly processed.
2.3.5 Assure that division by zero does not occur.
2.3.6 Include value zero in all calculations.
2.3.7 Assure that upper and lower values in ranges are handled correctly. (Using BVA)

2.4 ALPHANUMERIC FIELD CHECKS

2.4.1 Use blank and non-blank data.
2.4.2 Include lowest and highest values.
2.4.3 Include invalid characters & symbols.
2.4.4 Include valid characters.
2.4.5 Include data items with first position blank.
2.4.6 Include data items with last position blank.