website error messages HTTP errors

HTTP errors are sent to your web browser from a website if a problem is encountered when trying to view a webpage. If the webpage can't be displayed, Internet Explorer will display either the actual error page sent by the website or a friendly error message built into Internet Explorer. Here are some of the most common errors and ideas for how to solve the problem that's causing them.
The following table lists the most common HTTP errors that Internet Explorer displays. For information about HTTP protocols, error codes, and causes, go to the World Wide Web Consortium (W3C) website.
HTTP error message
What it means
The webpage cannot be found (HTTP 400)
Internet Explorer is able to connect to the web server, but the webpage can't be found because of a problem with the web address (URL). This error message often happens because the website address is typed incorrectly. Make sure the address is correct and try again.
The website declined to show this webpage (HTTP 403)

Internet Explorer is able to connect to the website, but Internet Explorer doesn't have permission to display the webpage. This can happen for a variety of reasons; here are some of the most common:
  • The website's administrator has to give you permission to view the page or the web server doesn't accept public webpage requests. If this is a website that you should have access to, contact the website administrator.
  • The webpage you're trying to view is generated by a program, such as a shopping cart or search engine, and the folder on the server the program is contained in isn't correctly configured by the website administrator.
  • You've typed a basic web address (for example, www.example.com), but the website doesn't have a default webpage (such as index.htm or default.html). Additionally, the website doesn't allow directory listing, which allows you to view files in a web folder.
The webpage cannot be found (HTTP 404)

Internet Explorer is able to connect to the website, but the webpage isn't found. This error is sometimes caused because the webpage is temporarily unavailable (in which case, you can try again later) or because the webpage has been deleted.


 The website cannot display the page (HTTP 405)
Internet Explorer is able to connect to the website, but the webpage content can't be downloaded to your computer. This is usually caused by a problem in the way the webpage was programmed.


Internet Explorer cannot read this webpage format (HTTP 406)

Internet Explorer is able to receive information from the website but the information isn't in a format that Internet Explorer can display.


The website is too busy to show the webpage (HTTP 408 or 409)

The server took too long to display the webpage or there were too many people requesting the same page. Try again later.
That webpage no longer exists (HTTP 410)

Internet Explorer is able to connect to the website, but the webpage can't be found. Unlike HTTP error 404, this error is permanent and was turned on by the website administrator. It's sometimes used for limited-time offers or promotional information.



The website cannot display the page (HTTP 500)


The website you're visiting had a server problem that prevented the webpage from displaying. It often occurs as a result of website maintenance or because of a programming error on interactive websites that use scripting.
The website is unable to display the webpage (HTTP 501 or 505)

Error 501 (HTTP 501 - Not Implemented) means that the website you're visiting isn't set up to display the content your browser is requesting. For example, the browser is asking for a file with a video extension (.AVI), but is telling the website it's looking for an HTML page.
Error 505 (HTTP 505 - Version Not Supported) means the website doesn't support the version of the HTTP protocol your browser uses to request the webpage (HTTP/1.1 being the most common).
Location: India

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"Sorry, Word Web App can't open this ... document because the service is busy." Office WebApp

Problem: Intermitten requests are not returning the pdf/word documents.  Most requests are working and occasionally 1 request doesn't work.  Every 4th request tries to get the pdf to display on Office Web Apps for a few minutes without any error message and then stops trying and displays the message "Sorry, Word Web App can't open this ... document because the service is busy." Initial Hypothesis: Originally I thought it was only happening to pdfs but it is happening to word and pdf documents (I don't have excel docs in my system).  My monitoring software SolarWinds is badly configured on my OWA servers as the monitor is showing green, drining into the servers monitoring the 2 application monitors are failing.  The server should go amber if either of the 2 applications fail and in turn red after 5 minutes.  At this point I notice that I can't log onto my 4 OWA/WCA server.  Web request are not being returned.  I look at my KEMP load balancer and it says al
Continue Read

Unable to create a "Send to Connection"- verification failed -url is a not a valid routing destination

ISSUE : Unable to successfully create a send to connection. When creating the Send to connection from Sharepoint 2010 Central Administration and click on Test URL for the Destination URL , we get the following error "verification failed -url is a not a valid routing destination" we see the following entry in the ULS logs Url validation failed for http://gmallya.test.com/sites/testrecordcenter/_vti_bin/OfficialFile.asmx   during Record and document center connection configuration with exception The request failed with HTTP status 401: Unauthorized .:  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)     at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)     at Microsoft.SharePoint.OfficialFileSoap.GetServerInfo()     at Microsoft.SharePoint.ApplicationPages.OfficialFileAdminPage.<>c__DisplayClass2.&l
Continue Read