Http status code - Revision history

Pchero: /* 404 Not Found */

2016-09-13T12:07:13Z

404 Not Found

← Older revision		Revision as of 12:07, 13 September 2016
Line 134:		Line 134:
	response is applicable.		response is applicable.
	</pre>		</pre>
	* RFC 7231 (https://tools.ietf.org/html/rfc7231#section-6.5.4)		: RFC 7231 (https://tools.ietf.org/html/rfc7231#section-6.5.4)
	* RFC 2616 (https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5)		: RFC 2616 (https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5)

	=== 405 Method Not Allowed ===		=== 405 Method Not Allowed ===

Pchero at 15:24, 9 August 2016

2016-08-09T15:24:10Z

← Older revision		Revision as of 15:24, 9 August 2016
Line 205:		Line 205:
	<references/>		<references/>

	[[category:~~programming~~]]		[[category:http]]

Pchero: /* 404 Not Found */

2016-08-09T08:22:49Z

404 Not Found

@@ Line 122: / Line 122: @@
 보안적인 이유로, 확인되지 않는 요청에 대한 응답, 인증 실패와 관련된 응답과 관련하여 404 코드로 응답할 수 있다.
 * RFC 7231 (https://tools.ietf.org/html/rfc7231#section-6.5.4)
 * RFC 2616 (https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5)

Pchero: /* 404 Not Found */

2016-08-09T08:22:00Z

404 Not Found

← Older revision		Revision as of 08:22, 9 August 2016
Line 121:		Line 121:
	: The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.		: The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.

	보안적인 ~~부분으로~~ 확인되지 않는 요청에 대한 응답, 인증 실패와 관련된 응답과 관련하여 404 코드로 응답할 수 있다.		보안적인 이유로, 확인되지 않는 요청에 대한 응답, 인증 실패와 관련된 응답과 관련하여 404 코드로 응답할 수 있다.
	* RFC 7231 (https://tools.ietf.org/html/rfc7231#section-6.5.4)		* RFC 7231 (https://tools.ietf.org/html/rfc7231#section-6.5.4)
	* RFC 2616 (https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5)		* RFC 2616 (https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5)

Pchero: /* 4XX Client error(요청 오류) */

2016-08-09T08:21:40Z

4XX Client error(요청 오류)

← Older revision		Revision as of 08:21, 9 August 2016
Line 97:		Line 97:
	: This code is used in the Resumable HTTP Requests Proposal to resume aborted PUT or POST requests.		: This code is used in the Resumable HTTP Requests Proposal to resume aborted PUT or POST requests.

	== 4XX Client error~~(요청 오류)~~ ==		== 4XX Client error ==
	4XX 클래스의 상태 코드는 클라이언트에 오류가 있음을 나타낸다.		요청 오류. 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.		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.

	* '''400 Bad Request(잘못된 요청~~)'''~~		=== 400 Bad Request ===
	: 서버가 요청의 구문을 인식하지 못했다.		잘못된 요청. 서버가 요청의 구문을 인식하지 못했다.
	: The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).		: The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

	* '''401 Unauthorized(RFC 7235)(권한 없음~~)'''~~		=== 401 Unauthorized(RFC 7235) ===
	: 이 요청은 인증이 필요하다. 서버는 로그인이 필요한 페이지에 대해 이 요청을 제공할 수 있다.		권한 없음. 이 요청은 인증이 필요하다. 서버는 로그인이 필요한 페이지에 대해 이 요청을 제공할 수 있다.
	: Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header filed containing a challenge applicable to the requested resource.		: Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header filed containing a challenge applicable to the requested resource.

	* '''402 Payment Required~~'''~~		=== 402 Payment Required ===
	: Reserved for future use. The original intention was the this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code is not usually used. YouTube uses this status if a particular IP address has made excessive requests, and requires the person to enter a CAPCHA.		: Reserved for future use. The original intention was the this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code is not usually used. YouTube uses this status if a particular IP address has made excessive requests, and requires the person to enter a CAPCHA.

	* '''403 Forbidden(금지됨~~)'''~~		=== 403 Forbidden ===
	: 요청 자체는 정상이지만 서버가 응답을 거부한 상태이다. 401 인증 오류와는 달리, 인증을 하더라도 같은 결과가 나올 것이다.		금지됨. 요청 자체는 정상이지만 서버가 응답을 거부한 상태이다. 401 인증 오류와는 달리, 인증을 하더라도 같은 결과가 나올 것이다.
	: The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.		: The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.

	* '''404 Not Found(찾을 수 없음~~)'''~~		=== 404 Not Found ===
	: 서버가 요청한 페이지를 찾을 수 없다. 예를 들어 서버에 존재하지 않는 페이지에 대한 요청이 있을 경우 서버는 이 코드를 제공한다.		찾을 수 없음. 서버가 요청한 페이지를 찾을 수 없다. 예를 들어 서버에 존재하지 않는 페이지에 대한 요청이 있을 경우 서버는 이 코드를 제공한다.
	: The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.		: The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.

	* ~~'''~~405 Method Not Allowed(허용되지 않는 방법~~)'''~~		보안적인 부분으로 확인되지 않는 요청에 대한 응답, 인증 실패와 관련된 응답과 관련하여 404 코드로 응답할 수 있다.
	: 요청에 지정된 방법을 사용할 수 없다.		* RFC 7231 (https://tools.ietf.org/html/rfc7231#section-6.5.4)
			* RFC 2616 (https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5)

			=== 405 Method Not Allowed ===
			허용되지 않는 방법. 요청에 지정된 방법을 사용할 수 없다.
	: A request was made of resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.		: A request was made of resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.

	* '''406 Not Acceptable(허용되지 않음~~)'''~~		=== 406 Not Acceptable ===
	: 요청한 페이지가 요청한 콘텐츠 특성으로 응답할 수 없다.		허용되지 않음. 요청한 페이지가 요청한 콘텐츠 특성으로 응답할 수 없다.
	: The requsted resource is only capable of generating content not acceptable according to the Accept headers sent in the request.		: The requsted resource is only capable of generating content not acceptable according to the Accept headers sent in the request.

	* '''407 Proxy Authentication Required(RFC 7235)(프록시 ~~인증 필요)'''~~		=== 407 Proxy Authentication Required(RFC 7235) ===
	: 이 상태 코드는 401(권한 없음)과 비슷하지만 요청자가 프록시를 사용하여 인증해야 한다. 서버가 이 응답을 표시하면 요청자가 사용할 프록시를 가리키는 것이기도 하다.		프록시 인증이 필요하다. 이 상태 코드는 401(권한 없음)과 비슷하지만 요청자가 프록시를 사용하여 인증해야 한다. 서버가 이 응답을 표시하면 요청자가 사용할 프록시를 가리키는 것이기도 하다.
	: The client must first authenticate itself with the proxy.		: The client must first authenticate itself with the proxy.

	* '''408 Request Timeout(요청 시간초과~~)'''~~		=== 408 Request Timeout ===
	: 서버의 요청 대기가 시간을 초과하였다.		요청 시간초과. 서버의 요청 대기가 시간을 초과하였다.
	: The server timed out waiting for the request. According to HTTP specifications: "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."		: The server timed out waiting for the request. According to HTTP specifications: "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."

Pchero: /* References */

2016-04-01T00:27:00Z

References

← Older revision		Revision as of 00:27, 1 April 2016
Line 189:		Line 189:
	<references/>		<references/>

	[[category:~~etc~~]]		[[category:programming]]

Pchero: /* 4XX Client error(요청 오류) */

2016-02-08T11:23:04Z

4XX Client error(요청 오류)

← Older revision		Revision as of 11:23, 8 February 2016
Line 114:		Line 114:

	* '''403 Forbidden(금지됨)'''		* '''403 Forbidden(금지됨)'''
	: 서버가 ~~요청을 거부하고 있다~~.		: 요청 자체는 정상이지만 서버가 응답을 거부한 상태이다. 401 인증 오류와는 달리, 인증을 하더라도 같은 결과가 나올 것이다.
	: The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.		: The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.

Pchero: /* 1XX Informational(조건부 응답) */

2015-11-12T12:54:56Z

1XX Informational(조건부 응답)

← Older revision		Revision as of 12:54, 12 November 2015
Line 8:		Line 8:

	* '''100 Continue(계속)'''		* '''100 Continue(계속)'''
	: 요청자는 요청을 계속해야 한다. 서버는 이 코드를 제공하여 요청의 첫 번째 부분을 받았으며 나머지를 기다리고 있음을 나타낸다.		: 서버는 Request header 를 수신한 상태이고, Client 는 Request body 를 송신해야 하는 상황이다(Request body 의 전송이 필요한 경우; 예를 들면 POST request 와 같은 경우). 요청자는 요청을 계속해야 한다. 서버는 이 코드를 제공하여 요청의 첫 번째 부분을 받았으며 나머지를 기다리고 있음을 나타낸다.

	* '''101 Switching Protocols(프로토콜 전환)'''		* '''101 Switching Protocols(프로토콜 전환)'''

Pchero: /* 5XX Server error(서버 오류) */

2015-11-12T12:06:09Z

5XX Server error(서버 오류)

← Older revision		Revision as of 12:06, 12 November 2015
Line 148:		Line 148:

	* '''503 Service Unavailable'''		* '''503 Service Unavailable'''
			: The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

	* '''504 Gateway Timeout'''		* '''504 Gateway Timeout'''
			: The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

	* '''505 HTTP Version Not Supported'''		* '''505 HTTP Version Not Supported'''
			: The server does not support the HTTP protocol version used in the request.

	* '''506 Variant Also Negotiates (RFC 2295)'''		* '''506 Variant Also Negotiates (RFC 2295)'''
			: Transparent content negotiation for the request results in a circular reference.

	* '''507 Insufficient Storage (WebDAV; RFC 4918)'''		* '''507 Insufficient Storage (WebDAV; RFC 4918)'''
			: The server is unable to store the representation needed to complete the request.

	* '''508 Loop Detected (WebDAV; RFC 5842)'''		* '''508 Loop Detected (WebDAV; RFC 5842)'''
			: The server detected an infinite loop while processing the request (sent in lieu of 208 Already Reported).

	* '''509 Banwidth Limit Exceeded (Apache bw/limited extension)'''		* '''509 Banwidth Limit Exceeded (Apache bw/limited extension)'''
			: This status code is not specified in any RFCs. Its use is unknown.

	* '''510 Not Extended (RFC 2774)'''		* '''510 Not Extended (RFC 2774)'''
			: Further extensions to the request are required for the server to fulfil it.

	* '''511 Network Authentication Required (RFC 6585)'''		* '''511 Network Authentication Required (RFC 6585)'''
			: The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., "captive portals" used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).

	* '''520 Unknown Error'''		* '''520 Unknown Error'''
			: This status code is not specified in any RFC and is returned by certain services, for instance Microsoft Azure and CloudFlare servers: "The 520 error is essentially a "catch-all" response for when the origin server returns something unexpected or something that is not tolerated/interpreted(protocol violation or empty response)."

	* '''522 Origin Connection Time-out'''		* '''522 Origin Connection Time-out'''
			: This status code is not specified in any RFCs, but is used by CloudFlare's reverse proxies to signal that a server connection timed out.

	* '''598 Network read timeout error(Unknwon)'''		* '''598 Network read timeout error(Unknwon)'''
			: This status code is not specified in any RFCs, but is used by Microsoft HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.

	* '''599 Network connect timeout error(Unknown)'''		* '''599 Network connect timeout error(Unknown)'''
			: This status code is not specified in any RFCs, but is used by Microsoft HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.

	== References ==		== References ==

Pchero at 14:26, 11 November 2015

2015-11-11T14:26:39Z

@@ Line 136: / Line 136: @@
 : 서버의 요청 대기가 시간을 초과하였다.
 : The server timed out waiting for the request. According to HTTP specifications: "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."
 == References ==