Friday, February 26, 2016

http error code overview

When accessing a web server or application, every HTTP request that is received by a server is responded to with an HTTP status code. HTTP status codes are three-digit codes, and are grouped into five different classes. The class of a status code can be quickly identified by its first digit:
  • 1xx: Informational
  • 2xx: Success
  • 3xx: Redirection
  • 4xx: Client Error
  • 5xx: Server Error

1xx: Information

Message: 100 Continue
Description: The server has received the request headers, and the client should proceed to send the request body

Message: 101 Switching Protocols
Description: The requester has asked the server to switch protocols

Message: 103 Checkpoint
Description: Used in the resumable requests proposal to resume aborted PUT or POST requests

2xx: Successful

Message: 200 OK

Description: 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.

Message: 201 Created
Description: 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.

Message: 202 Accepted

Description: 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.

Message: 203 Non-Authoritative Information
Description: 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).

Message: 204 No Content
Description: 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.

Message: 205 Reset Content
Description: 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.

Message: 206 Partial Content
Description: The server has fulfilled the partial GET request for the resource. The request MUST have included a Range header field indicating the desired range, and MAY have included an If-Range header field to make the request conditional.

The response MUST include the following header fields:

      - Either a Content-Range header field 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, 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.

A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.

Thursday, February 25, 2016

error code 500 : internal server error

The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server, but the server could not be more specific on what the exact problem is.

The 500 error is the Web servers way of saying “Something went wrong but I can’t tell you what, sorry.” This is what we call a “server-side” error. That means that there is something wrong with the server who is hosting the website. It is an extremely general error usually caused by configuration issues with the websites programming, PHP or system permissions.




  • Check for the resolution:Permissions: Many times you will find that the permission setting on one of your folders is set incorrectly. It could be a simple fix as switching a file/folder permission from 777 to 755 or vice versa. In most cases permission sets of 777 are extremely unsafe and can allow even an amateur hacker to access your files and put malicious code in it. Make sure to check with your hosting provider for specific information about permissions set as some servers have different regulations.
  • Incorrectly configured .htaccess: Oftentimes you will receive an internal server error when the htaccess file is configured incorrectly. For PrestaShop purposes, the main culprits of the htaccess errors are “URL Rewrite” settings or Friendly URL enabling. The htaccess syntax is very strict so even one wrong character or command will cause the server to return an Internal Error 500. Make a backup of your htaccess and regenerate the htaccess file either through the back office or by toggling the Enable Friendly URL option.
  • Server timeout: Every server has their own timeout setting, which sets the time that any given script can run. If the function or script crosses that limit, you will receive an error 500. You should contact your hosting provider and inquire about changing the limit, at least temporarily.


Wednesday, February 24, 2016

http error code 403 : How to fix 403 error

The 403 Forbidden error is an HTTP statuscode which means that accessing the page or resource you were trying to reach is absolutely forbidden for some reason. This article contains basic troubleshooting instructions for403 Forbidden errors.



The 403 Forbidden error is an HTTP status code that means that accessing the page or resource you were trying to reach is absolutely forbidden for some reason.


Different web servers report 403 errors in different ways, the majority of which I've listed below. Website owners are also welcome to customize HTTP 403 errors but that's not too common.

Cause of 403 Forbidden Errors


403 errors are almost always caused by issues where you're trying to access something that you don't have access to. The 403 error is essentially saying "Go away and don't come back here."

Note: Microsoft IIS web servers provide more specific information about the cause of 403 Forbidden errors by suffixing a number after the 403 as in HTTP Error 403.14 - Forbidden which means Directory listing denied. You can see a complete list here.

How To Fix the 403 Forbidden Error

Check for URL errors and make sure you're specifying an actual web page file name and extension, not just a directory. Most websites are configured to disallow directory browsing so a 403 Forbidden message when trying to display a folder instead of a specific page is normal and expected.

Important: This is, by far, the most common reason for a web site to return the 403 Forbidden error. Be sure you fully explore this possibility before investing time in the troubleshooting below.

Tip: If you operate the website in question, and you want to prevent 403 errors in these cases, enable directory browsing in your web server software.

Clear your browser's cache. Issues with a cached version of the page you're viewing could be causing 403 Forbidden issues.

Log in to the website, assuming it's possible and appropriate to do so. A 403 Forbidden message could mean that you need additional access before you can view the page.

Typically, a website produces a 401 Unauthorized error when special permission is required but sometimes a 403 Forbidden is used instead.

Clear your browser's cookies, especially if you typically log in to this website and logging in again (the last step) didn't work.

Note: While we're talking about cookies, be sure you have them enabled in your browser, or at least for this website, if you do actually log in to access this page. The 403 Forbidden error in particular indicates that cookies may be involved in obtaining proper access.

Contact the website directly. It's possible that the 403 Forbidden error is a mistake, everyone else is seeing it too, and the website isn't yet aware of the problem.

See my Website Contact Information list for contact information for lots of popular websites. Most sites have support-based accounts on social networking sites, making it really easy to get a hold of them. Some even have support email addresses and telephone numbers.

Tip: Twitter is usually abuzz with talk when a site goes down completely, especially if it's a popular site. The best way to focus in on talk about a downed site is by searching for #websitedown on Twitter, as in #amazondown or #facebookdown. While this trick certainly won't work if Twitter is down with a 403 error, it's great for checking on the status of other downed sites.

Contact your ISP if your still getting the 403 error, especially if you're pretty sure that the website in question is working for others right now.

It's possible that your public IP address, or your entire Internet Service Provider, has been blacklisted, a situation that could produce a 403 Forbidden error, usually on all pages on one or more sites.

Come back later. Once you've verified that the page you're accessing is the correct one and that the HTTP 403 error is being seen by more than just you, just revisit the page on a regular basis until the problem is fixed.
Still Getting 403 Errors?

If you've followed all of the advice above but are still receiving a 403 Forbidden error when accessing a certain webpage or site, see Get More Help for information about contacting me on social networks or via email, posting on tech support forums, and more.

Be sure to let me know that the error is an HTTP 403 error and what steps, if any, you've already taken to fix the problem.


Tuesday, February 23, 2016

google chrome Error 0xa0430721, How can i fix it?

Step1: Open your Application Data Folder. 

For Windows XP: %USERPROFILE%\Application Data\Local
For Windows Vista/7: %USERPROFILE%\AppData\Local

Step2: Delete Google Folder (If you have other Google Applications, open the folder and delete "Chrome").

Step3: Open Task Manager>Processes (If running on Windows Vista/7, select "Show Processes From All Users" and click "Allow")

Click on "Description" (on top where you see Image Name, User Name etc..)
Scroll Down until you see anything with the Description "Google".
End each process 1 by 1.

Click on "Image Name" (on top where you see Image Name, User Name etc..)
Scroll Down until you see anything with the Image Name "Google"
End each process 1 by 1.

Step 4: Go to http://www.google.com/chrome/
and install Google Chrome.

Reference: http://www.google.com

Get List Of All Error Codes In SQL Server

We can get all the error messages by running the below SQL command:-

USE master
GO
SELECT * FROM dbo.sysmessages

This will return Error numbers that uniquely identifies the error, Severity level which defines nature of the error, Dlevel is used for internal purpose,  Description defines explanation of the error that occurred and Mslangid is system message group ID.

Output: