"HTTP"의 두 판 사이의 차이
둘러보기로 가기
검색하러 가기
Pythagoras0 (토론 | 기여) (→노트: 새 문단) |
Pythagoras0 (토론 | 기여) |
||
(같은 사용자의 중간 판 하나는 보이지 않습니다) | |||
61번째 줄: | 61번째 줄: | ||
===소스=== | ===소스=== | ||
<references /> | <references /> | ||
+ | |||
+ | ==메타데이터== | ||
+ | ===위키데이터=== | ||
+ | * ID : [https://www.wikidata.org/wiki/Q8777 Q8777] | ||
+ | ===Spacy 패턴 목록=== | ||
+ | * [{'LOWER': 'hypertext'}, {'LOWER': 'transfer'}, {'LEMMA': 'Protocol'}] | ||
+ | * [{'LEMMA': 'HTTP'}] | ||
+ | * [{'LEMMA': 'http://'}] | ||
+ | * [{'LOWER': 'http'}, {'LEMMA': ':'}] |
2021년 2월 17일 (수) 00:44 기준 최신판
노트
- From these humble beginnings in 1991, HTTP took on a life of its own and evolved rapidly over the coming years.[1]
- Similarly, a parallel HTTP Working Group (HTTP-WG) was established within the IETF to focus on improving the HTTP protocol.[1]
- Hence, the "hypertext transfer" part of HTTP became a misnomer not long after its introduction.[1]
- In reality, HTTP has quickly evolved to become a hypermedia transport, but the original name stuck.[1]
- HTTP stands for Hypertext Transfer Protocol.[2]
- The first version of HTTP had one method that was then named GET.[2]
- HTTP is also designed for use as an intermediation protocol for translating communication to and from non-HTTP information systems.[3]
- HTTP is defined as a stateless protocol, meaning that each request message can be understood in isolation.[3]
- HTTP does not place a predefined limit on the length of a request-line, as described in Section 2.5.[3]
- This document serves as the specification for the Internet media types "message/http" and "application/http".[3]
- Hypertext Transfer Protocol (HTTP) is the application-level protocol that is used to transfer data on the Web.[4]
- HTTP comprises the rules by which Web browsers and servers exchange information.[4]
- Hypertext Transfer Protocol is the protocol used to allow communication with Web sites.[5]
- The Hypertext Transfer Protocol, or HTTP, is the most widely used Application layer protocol in the world today.[6]
- Google now recommends that all websites use HTTPS connections as opposed to standard HTTP.[7]
- Secure HTTP is a secure message-oriented communications protocol designed for use in conjunction with HTTP.[8]
- S-HTTP supports interoperation among a variety of implementations, and is compatible with HTTP.[8]
- Syntactically, Secure HTTP messages are the same as HTTP, consisting of a request or status line followed by headers and a body.[8]
- If the inner message is an S-HTTP message, then the content type shall be 'application/s-http'.[8]
- HTTP helps web users retrieve web pages.[9]
- The current version of HTTP has improved efficiency by allowing a host to maintain a connection for more than one transfer if appropriate.[10]
- HTTP, in full HyperText Transfer Protocol, standard application-level protocol used for exchanging files on the World Wide Web.[11]
- HTTP was originally proposed in 1989 by Tim Berners-Lee, who was a coauthor of the 1.0 specification.[11]
- The Hypertext Transfer Protocol (HTTP) is a networking protocol for distributed, collaborative, hypermedia information systems.[12]
- In HTTP, a web browser, for example, acts as a client, while an application running on a computer hosting a web site functions as a server.[12]
- HTTP defines methods to indicate what action the client wants to perform.[13]
- Since HTTP is an application layer protocol, it defines how requests and responses are communicated, but not how the data is transported.[13]
- The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems.[14]
- IIS 4 supports a new version of this protocol called HTTP 1.1, which has new features that make it more efficient.[15]
- In May 2015 a new standard of HTTP was published as RFC 7540 – HTTP/2.[15]
- Hypertext Transfer Protocol defines a set of request methods to indicate the desired action to be performed for a given resource.[15]
- The first documented version of HTTP was HTTP V0.9 (1991).[15]
- HTTP uses a server-client model.[16]
- URLs that begin with "http://" are accessed over the standard hypertext transfer protocol and use port 80 by default.[16]
- Simply put, it is the secure version of HTTP.[17]
- Information is exchanged between clients and servers in the form of Hypertext documents, from which HTTP gets its name.[18]
- The first version of HTTP caused considerable overhead.[19]
- Hypertext Transfer Protocol (HTTP) is an application-layer protocol for transmitting hypermedia documents, such as HTML.[20]
- HTTP is a stateless protocol, meaning that the server does not keep any data (state) between two requests.[20]
- : It means, any type of data can be sent by HTTP as long as both the client and the server know how to handle the data content.[21]
- HTTP is stateless: As mentioned above, HTTP is connectionless and it is a direct result of HTTP being a stateless protocol.[21]
- HTTP is a protocol which allows the fetching of resources, such as HTML documents.[22]
- Designed in the early 1990s, HTTP is an extensible protocol which has evolved over time.[22]
- HTTP is a client-server protocol: requests are sent by one entity, the user-agent (or a proxy on behalf of it).[22]
- HTTP is stateless: there is no link between two requests being successively carried out on the same connection.[22]
- This appendix provides a short introduction to a few Hypertext Transfer Protocol (HTTP) basics.[23]
- HTTP is based on a request/response model.[23]
- Previous versions of the server supported HTTP 1.0.[23]
- As soon as a web user opens their web browser, the user is indirectly making use of HTTP.[24]
- HTTP is an application protocol that runs on top of the TCP/IP suite of protocols (the foundation protocols for the Internet).[24]
- The latest version of HTTP is HTTP/2, which was published in May 2015.[24]
- Development of HTTP was initiated by Tim Berners-Lee at CERN in 1989.[25]
- HTTP is designed to permit intermediate network elements to improve or enable communications between clients and servers.[25]
- HTTP is an application layer protocol designed within the framework of the Internet protocol suite.[25]
- The first version of HTTP, referred to as HTTP/0.9, was a simple protocol for raw data transfer across the Internet.[26]
- The "http" scheme is used to locate network resources via the HTTP protocol.[26]
- On closer inspection, shouldn't the BNF for that section (14.18) be "rfc1123-date" and not "HTTP-date"?[26]
- HTTP applications MUST accept CRLF, bare CR, and bare LF as being representative of a line break in text media received via HTTP.[26]
소스
- ↑ 1.0 1.1 1.2 1.3 HTTP: Brief History of HTTP
- ↑ 2.0 2.1 Everything You Need to Know About HTTP (Hypertext Transfer Protocol)
- ↑ 3.0 3.1 3.2 3.3 RFC 7230: Hypertext Transfer Protocol (HTTP
- ↑ 4.0 4.1 What is Hypertext Transfer Protocol (HTTP)?
- ↑ Changing the Hypertext Transfer Protocol
- ↑ What is the HyperText Transfer Protocol (HTTP)
- ↑ HTTPS: Hypertext Transfer Protocol Secure. SEO Glossary
- ↑ 8.0 8.1 8.2 8.3 The Secure HyperText Transfer Protocol
- ↑ What Is The Definition Of HTTPS?
- ↑ 3.3 Hypertext transfer protocol (HTTP)
- ↑ 11.0 11.1 HTTP | computer science
- ↑ 12.0 12.1 What is Hypertext Transfer Protocol (HTTP)?
- ↑ 13.0 13.1 Hypertext Transfer Protocol (HTTP)
- ↑ RFC2616: Hypertext Transfer Protocol -- HTTP/1.1
- ↑ 15.0 15.1 15.2 15.3 Hypertext Transfer Protocol (HTTP) – Network Encyclopedia
- ↑ 16.0 16.1 HTTP (Hypertext Transfer Protocol) Definition
- ↑ What is HyperText Transfer Protocol?
- ↑ What Is HTTP? Protocol for Internet Data Transfer
- ↑ Definition of HTTP
- ↑ 20.0 20.1 HTTP
- ↑ 21.0 21.1 Tutorialspoint
- ↑ 22.0 22.1 22.2 22.3 An overview of HTTP - HTTP
- ↑ 23.0 23.1 23.2 Hypertext Transfer Protocol
- ↑ 24.0 24.1 24.2 What is HTTP (Hypertext Transfer Protocol)?
- ↑ 25.0 25.1 25.2 Hypertext Transfer Protocol
- ↑ 26.0 26.1 26.2 26.3 Hypertext Transfer Protocol -- HTTP/1.1
메타데이터
위키데이터
- ID : Q8777
Spacy 패턴 목록
- [{'LOWER': 'hypertext'}, {'LOWER': 'transfer'}, {'LEMMA': 'Protocol'}]
- [{'LEMMA': 'HTTP'}]
- [{'LEMMA': 'http://'}]
- [{'LOWER': 'http'}, {'LEMMA': ':'}]