> For the complete documentation index, see [llms.txt](https://krjaeh0.gitbook.io/j-log/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://krjaeh0.gitbook.io/j-log/programming/cs_basics/web_technologies/http-and-urls/rfc_2616_code.md).

# RFC\_2616\_Code

HTTP 표준 RFC 2616은 대략 40여개의 상태 코드를 정의하며, 각각은 첫 번째 자릿수에 따라 5개의 클래스로 분류됩니다.

| **상태 코드** | **설명**                                     | **대표 예시**                                                                                                                                                                            |
| --------- | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 1xx       | 요청을 제대로 받았고, 처리가 진행 중임                     |                                                                                                                                                                                      |
| 2xx       | 요청이 제대로 처리됨                                | - 200 (OK): 성공                                                                                                                                                                       |
| 3xx       | 요청을 처리하려면, 클라이언트가 추가 동작을 취해야 함.            | - 302 (Found): 다른 URL로 갈 것                                                                                                                                                           |
| 4xx       | 클라이언트가 잘못된 요청을 보내어 처리에 실패했습니다.             | <p>- 400 (Bad Request): 요청이 문법에 맞지 않음<br><br>- 401 (Unauthorized): 클라이언트가 요청한 리소스에 대한 인증이 실패함<br><br>- 403 (Forbidden): 클라이언트가 리소스에 요청할 권한이 없음<br><br>- 404 (Not Found): 리소스가 없음</p> |
| 5xx       | 클라이언트의 요청은 유효하지만, 서버에 에러가 발생하여 처리에 실패했습니다. | <p>- 500 (Internal Server Error): 서버가 요청을 처리하다가 에러가 발생함<br><br>- 503 (Service Unavailable): 서버가 과부하로 인해 요청을 처리할 수 없음</p>                                                             |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://krjaeh0.gitbook.io/j-log/programming/cs_basics/web_technologies/http-and-urls/rfc_2616_code.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.