> For the complete documentation index, see [llms.txt](https://applezulab.netdpi.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://applezulab.netdpi.net/linux-prog/http-rfcs.md).

# 與 HTTP 協定有關的 RFC

| <p>RFC 1521, MIME (Multipurpose Internet Mail Extensions): <http://www.rfc-editor.org/rfc/rfc1521.txt> <br>RFC 1808, Relative Uniform Resource Locators: <http://www.rfc-editor.org/rfc/rfc1808.txt> <br>RFC 1945, HTTP/1.0: <http://www.rfc-editor.org/rfc/rfc1945.txt> <br>RFC 2109, HTTP State Management Mechanism: <http://www.rfc-editor.org/rfc/rfc2145.txt> <br>RFC 2246, The TLS Protocol: <http://www.rfc-editor.org/rfc/rfc2246.txt> <br>RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax: <http://www.rfc-editor.org/rfc/rfc2396.txt> <br>RFC 2518, HTTP Extensions for Distributed Authoring: <http://www.rfc-editor.org/rfc/rfc2518.txt> <br>RFC 2585, Internet X.509 Public Key Infrastructure: <http://www.rfc-editor.org/rfc/rfc2585.txt> <br>RFC 2616, HTTP/1.1: <http://www.rfc-editor.org/rfc/rfc2616.txt> <br>RFC 2617, Basic and Digest Access Authentication: <http://www.rfc-editor.org/rfc/rfc2617.txt> <br>RFC 2774, HTTP Extension Framework: <http://www.rfc-editor.org/rfc/rfc2774.txt> <br>RFC 2817, Upgrading to TLS Within HTTP/1.1: <http://www.rfc-editor.org/rfc/rfc2817.txt> <br>RFC 2818, HTTP Over TLS: <http://www.rfc-editor.org/rfc/rfc2818.txt> <br>RFC 2964, Use of HTTP State Management: <http://www.rfc-editor.org/rfc/rfc2964.txt> <br>RFC 2965, HTTP State Management Mechanism: <http://www.rfc-editor.org/rfc/rfc2965.txt> <br>RFC 3253, Versioning Extensions to WebDAV: <http://www.rfc-editor.org/rfc/rfc3253.txt> <br><br>參考文獻： Chris Shiflett, HTTP Developer's Handbook.</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://applezulab.netdpi.net/linux-prog/http-rfcs.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.
