Downloaded 75 times
Uploaded byLuavis Kang
Http
HTTP is the Hypertext Transfer Protocol used globally for communication on the World Wide Web. It was first proposed in 1989 and has undergone several revisions with HTTP/1.1 being the most widely used version today. HTTP uses packets to transfer hypertext requests and responses between clients and servers, with the request containing a method like GET or POST and a URL, and the response containing a status code and optional headers and content.
More Related Content
![[SWMaestro 100+ 발표자료] 테스트하기](https://cdn.slidesharecdn.com/ss_thumbnails/100-171107013426-thumbnail.jpg?width=640&height=640&fit=bounds)
Http
- 1. Luavis http://github.com/luavis HTTP Hyper TextTransfer Protocol
- 2. Luavis http://github.com/luavis HTTP Hyper TextTransfer Protocol History Packet Method Status Code Headers 2
- 3. Hyper Text HTML Hyper TextMarkup Language
- 4. Hyper Text Transfer 하이퍼텍스트를옮기는 프로토콜 Protocol
- 5.
- 6. Tim Berners-Lee andhis team at CERN
- 7. - Berners-Lee firstproposed the "WorldWideWeb" project in 1989. - The first documented version of HTTP was HTTP V0.9 (1991). - Dave Raggett led the HTTP Working Group (HTTP WG) in 1995. - RFC 1945 officially introduced and recognized HTTP V1.0 in 1996. - The HTTP/1.1, RFC 2068 was officially released in January 1997
- 8.
- 9.
- 10.
- 11. Packet It is textbased HTTP/1.1 200 OK Date: Thu, 20 May 2010 01:43:23 GMT Server: Nginx/1.3 Cache-Control: no-cache, no-Store <html> <p>hello World</p> </html> GET / HTTP/1.1
- 12. Request packet POST /HTTP/1.1 Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0 Accept-Encoding:gzip, deflate, sdch Accept-Language:ko-KR,ko;q=0.8,en-US;q=0.6,en;q=0.4,ja;q=0.2 Cache-Control:max-age=0 Connection:keep-alive Host:www.w3.org Referer:https://www.google.co.kr/ User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.3 search=google&utf-8=&page=10
- 13. POST / HTTP/1.1 Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0 Accept-Encoding:gzip,deflate, sdch Accept-Language:ko-KR,ko;q=0.8,en-US;q=0.6,en;q=0.4,ja;q=0.2 Cache-Control:max-age=0 Connection:keep-alive Host:www.w3.org Referer:https://www.google.co.kr/ User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.3 search=google&utf-8=&page=10 Request packet
- 14. Request packet POST /HTTP/1.1 Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0 Accept-Encoding:gzip, deflate, sdch Accept-Language:ko-KR,ko;q=0.8,en-US;q=0.6,en;q=0.4,ja;q=0.2 Cache-Control:max-age=0 Connection:keep-alive Host:www.w3.org Referer:https://www.google.co.kr/ User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.3 search=google&utf-8=&page=10
- 15. Request packet POST /HTTP/1.1 Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0 Accept-Encoding:gzip, deflate, sdch Accept-Language:ko-KR,ko;q=0.8,en-US;q=0.6,en;q=0.4,ja;q=0.2 Cache-Control:max-age=0 Connection:keep-alive Host:www.w3.org Referer:https://www.google.co.kr/ User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.3 search=google&utf-8=&page=10
- 16. HTTP/1.1 200 OK Content-Language:en Content-Location:O-HTTP-charset.en.php Content-Type:text/html;charset=UTF-8 Date:Tue, 19 May 2015 15:23:39 GMT P3P:policyref="http://www.w3.org/2014/08/p3p.xml" Server:Apache/2 TCN:choice Transfer-Encoding:chunked Vary:negotiate,accept-language <html> <p>hello World</p> </html> Response packet
- 17. HTTP/1.1 200 OK Content-Language:en Content-Location:O-HTTP-charset.en.php Content-Type:text/html;charset=UTF-8 Date:Tue, 19 May 2015 15:23:39 GMT P3P:policyref="http://www.w3.org/2014/08/p3p.xml" Server:Apache/2 TCN:choice Transfer-Encoding:chunked Vary:negotiate,accept-language <html> <p>hello World</p> </html> Response packet
- 18. HTTP/1.1 200 OK Content-Language:en Content-Location:O-HTTP-charset.en.php Content-Type:text/html;charset=UTF-8 Date:Tue, 19 May 2015 15:23:39 GMT P3P:policyref="http://www.w3.org/2014/08/p3p.xml" Server:Apache/2 TCN:choice Transfer-Encoding:chunked Vary:negotiate,accept-language <html> <p>hello World</p> </html> Response packet
- 19. HTTP/1.1 200 OK Content-Language:en Content-Location:O-HTTP-charset.en.php Content-Type:text/html;charset=UTF-8 Date:Tue, 19 May 2015 15:23:39 GMT P3P:policyref="http://www.w3.org/2014/08/p3p.xml" Server:Apache/2 TCN:choice Transfer-Encoding:chunked Vary:negotiate,accept-language <html> <p>hello World</p> </html> Response packet
- 20.
- 21.
- 22.
- 23.
- 24. GET / HTTP/1.1 Method Path Version Requestpacket Method GET HEAD POST PUT DELETE TRACE OPTIONS CONNECT PATCH RESTFUL Usage
- 25. GET HEAD PUT DELETE OPTIONS CONNECT 자료를 요청 Requests arepresentation of the specified resource. Asks for the response identical to the one that would correspond to a GET request, but without the response body. 자료의 존재 요청 POST TRACE 자료 업로드 Requests that the server accept the entity enclosed in the request 자료 수정 Requests that the enclosed entity be stored under the supplied, If already existing resource, it is modified 자료 삭제 Deletes the specified resource Echoes back the received request changes or additions 서버 확인 Returns the HTTP methods that the server supports for the specified URL 가능한 메소드 확인 Converts the request connection to a transparent TCP/IP tunnel Applies partial modifications to a resource PATCH 부분적 수정
- 26. GET 자료를 요청 Requests arepresentation of the specified resource. C has published guidance principles on this distinction, saying, "Web applicatio
- 27. HEAD Asks for theresponse identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content. 자료의 존재 요청
- 28. Requests that theserver accept the entity enclosed in the request as a new subordinate of the web resource identified by the URI. The data POSTed might be, for example, an annotation for existing resources; a message for a bulletin board, newsgroup, mailing list, or comment thread; a block of data that is the result of submitting a web form to a data-handling process; or an item to add to a database. POST 자료 업로드
- 29. Requests that theenclosed entity be stored under the supplied URI. If the URI refers to an already existing resource, it is modified; if the URI does not point to an existing resource, then the server can create the resource with that URI. PUT 자료 수정
- 30. Deletes the specifiedresource. DELETE 자료 삭제
- 31. eived request sothat a client can see what (if any) changes or additions have been made by i TRACE 서버 확인
- 32. Converts the requestconnection to a transparent TCP/IP tunnel, usually to facilitate SSL-encrypted communication (HTTPS) through an unencrypted HTTP proxy. See HTTP CONNECT tunneling. OPTIONS 가능한 메소드 확인
- 33. Returns the HTTPmethods that the server supports for the specified URL. This can be used to check the functionality of a web server by requesting instead of a specific resource. CONNECT
- 34. Applies partial modificationsto a resource. PATCH 부분적 수정
- 35.
- 36.
- 37.
- 38. HTTP/1.1 Content-Language:en Content-Location:O-HTTP-charset.en.php Content-Type:text/html; charset=UTF-8 Date:Tue, 19May 2015 15:23:39 GMT P3P:policyref="http://www.w3.org/2014/08/p3p.xml" Server:Apache/2 TCN:choice Transfer-Encoding:chunked Vary:negotiate,accept-language <html> <p>hello World</p> </html> Response packet 200 OK
- 39. HTTP/1.1 Content-Language:en Content-Location:O-HTTP-charset.en.php Content-Type:text/html; charset=UTF-8 Date:Tue, 19May 2015 15:23:39 GMT P3P:policyref="http://www.w3.org/2014/08/p3p.xml" Server:Apache/2 TCN:choice Transfer-Encoding:chunked Vary:negotiate,accept-language <html> <p>hello World</p> </html> Response packet 200 OK
- 40.
- 41.
- 42. 100 200 300400 500 Status code <response code>
- 43. Informational 1xx 100 Continue 서버는이 코드를 제공하여 요청의 첫 번째 부분을 받았으며 나머지를 기다리고 있음을 나타낸 101 Switching Protocols 서버에 프로토콜 전환을 요청했으며 서버는 이를 승인하는 중이다.
- 44. 200 OK 이는 주로서버가 요청한 페이지를 제공했다는 의미로 쓰인 201 Created 서버가 새 리소스를 작성했다. 202 Accepted 접수했지만 아직 처리하지 않았다. 203 Non-Authoritative Information 다른 소스에서 수신된 정보를 제공하고 있다. 204 No Content 처리했지만 콘텐츠를 제공하지 않는다. 205 Reset Content 문서 보기를 재설정할 것을 요구한다 206 Partial Content 일부만 성공적으로 처리했다. Successful 2xx
- 45. 300 Multiple Choices 서버가사용자 에이전트에 따라 수행할 작업을 선택하거나 요청자가 선택할 수 있는 작업 목록을 제공한다. 301 Moved Permanently GET 또는 HEAD 요청에 대한 응답으로 이 응답을 표시하면 요청자가 자동으로 새 위치로 전달된다 302 Found 요청자는 향후 요청 시 원래 위치를 계속 사용해야 한다. 304 Not Modified 마지막 요청 이후 요청한 페이지는 수정되지 않았다. 307 Temporary Redirect 현재 서버가 다른 위치의 페이지로 요청에 응답하고 있지만 요청자는 향후 요청 시 원래 위치를 계속 사용해야 한다. Redirection 3xx
- 46. 400 Bad Request 서버가요청의 구문을 인식하지 못했다. 401 Unauthorized 서버는 로그인이 필요한 페이지에 대해 이 요청을 제공할 수 있다. 404 Not Found 서버가 요청한 페이지를 찾을 수 없다. 405 Method Not Allowed 요청에 지정된 방법을 사용할 수 없다. 408 Request Timeout 서버의 요청 대기가 시간을 초과하였다. 413 Request Entity Too Large 요청이 너무 커서 서버가 처리할 수 없다. Client Error 4xx
- 47. Server Error 5xx500 Internal Server Error 서버에 오류가 발생하여 요청을 수행할 수 없다. 501 Not Implemented 서버에 요청을 수행할 수 있는 기능이 없다. 502 Bad Gateway 서버가 게이트웨이나 프록시일때, 업스트림 서버에서 잘못된 응답을 받았다. 503 Service Unavailable 서버가 오버로드되었거나 유지관리를 위해 다운됨. 504 Gateway Timeout 서버가 게이트웨이나 프록시일때, 응답을 제때 못 받았다. 505 HTTP Version Not Supported 사용된 HTTP 프로토콜 버전을 지원하지 않는다.
- 48.
- 49.
- 50.
- 51.
- 52. Server : 어떤서버 프로그램의 정보를 클라이언트에게 제공 Host : 요청하는 도메인을 제공 ex) Server: nginx/1.7 ex) Host: www.example.com Location : Moved 일 경우 이동할 주소를 제공 ex) Location: www.example.com ex) Date: Wed, 15 Nov 1995 06:25:24 GMT Date : 서버의 시간을 제공
- 53.
- 54.
- 55.
- 56.
- 57. Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 MIME TYPE 전자우편은7비트 ASCII 문자를 사용하여 전송되기 때문에, 8비트 이상의 코드를 사용하는 문자나 이진 파일들은 MIME 포맷으로 변환되어 SMTP로 전송된다.
- 58. Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 ASCII,EUC-KR, EUC-JP, CP949, UTF-8…etc
- 59. Content-Type: text/html; charset=utf-8 서버가클라이언트에게 보내는 내용의 type을 알려줌
- 60.
- 61.
- 62. compress – UNIX"compress" program method deflate – compression based on the deflate algorithm, wrapped inside the zlib data format exi – W3C Efficient XML Interchange gzip – GNU zip format. This method is the most broadly supported identity – No transformation is used. This is the default value for content coding. pack200-gzip – Network Transfer Format for Java Archives. bzip2 – compression based on the free bzip2 format, supported by lighttpd lzma – compression based on (raw) LZMA is available in Opera 20, and in elinks via a compile-time option peerdist – Microsoft Peer Content Caching and Retrieval sdch – Google Shared Dictionary Compression for HTTP, based on VCDIFF. xz - LZMA2-based content compression, supported by a non-official Firefox patch. Accept-Encoding: gzip, deflate, sdch
- 63. Content-Encoding: gzip 서버가 클라이언트에게보내는 내용의 압축방식을 알려줌
- 64. Accept-Language 클라이언트가 서버에게 받을수 있는 언어의 종류를 보냄
- 65.
- 66. Accept-Language ISO 639-1 Code 2글자로나타낸 언어코드 ko, en, ja, zh…
- 67. Accept-Language ISO 639-1 Code 2글자로나타낸 언어코드 ko-kr, en-us, en-gb, ja-jp, zh-cn, zh-tw… Accept-Language: ko-kr,ko;q=0.8,en-us;q=0.5,en;q=0.3
- 68. Content-Language: ko-kr 서버가 클라이언트에게보내는 내용의 언어를 알려줌
- 69. Content-Length: 23021 서버가 클라이언트에게보내는 내용의 크기를 바이트 단위로 알려줌
- 70.
- 71. User-Agent 클라이언트가 서버에게 보내는브라우저의 정보를 알려줌
- 72.
- 73.
- 74.
- 75. Mozilla/2.02Gold (Win95; I) Mozilla/1.22(compatible; MSIE 2.0; Windows 95)
- 76. Mozilla/2.02Gold (Win95; I) Mozilla/1.22(compatible; MSIE 2.0; Windows 95) ????
- 77. Mozilla/2.02Gold (Win95; I) Mozilla/1.22(compatible; MSIE 2.0; Windows 95) osh; U; PPC Mac OS X; en) AppleWebKit/312.8.1 (KHTML, like G
- 78. Mozilla/2.02Gold (Win95; I) 64;Trident/4.0; SLCC2; .NET CLR 2.0.50727; Media Center PC 6 osh; U; PPC Mac OS X; en) AppleWebKit/312.8.1 (KHTML, like G
- 79. Mozilla/2.02Gold (Win95; I) 64;Trident/4.0; SLCC2; .NET CLR 2.0.50727; Media Center PC 6 osh; U; PPC Mac OS X; en) AppleWebKit/312.8.1 (KHTML, like G ????
- 80. la/5.0 (Windows NT6.1; WOW64; Trident/7.0; AS; rv:11.0) like G osh; U; PPC Mac OS X; en) AppleWebKit/312.8.1 (KHTML, like G Mac OS X 10_8_0) AppleWebKit/536.3 (KHTML, like Gecko) Chro
- 81.
- 82. 서버와 클라이언트 간의데이터를 저장해둠 Cookie
- 84.
- 85.
- 86. Cookie: user=luavis; grade=2; 클라이언트가서버에게 쿠키값을 알려줌
- 87. Set-Cookie: lu=Rg3vHJZnehYLjVg7qi3bZjzg; Expires=Tue,15-Jan-2013 2 Set-Cookie: made_write_conn=1295214458; Path=/; Domain=.example.co Set-Cookie: reg_fb_gate=deleted; Expires=Thu, 01-Jan-1970 00:00:01 GM 서버가 클라이언트에게 쿠키값을 설정하라 지시
- 88. Set-Cookie: lu=Rg3vHJZnehYLjVg7qi3bZjzg; Expires=Tue,15-Jan-2013 2 Set-Cookie: made_write_conn=1295214458; Path=/; Domain=.example.co Set-Cookie: reg_fb_gate=deleted; Expires=Thu, 01-Jan-1970 00:00:01 GM
- 89. Set-Cookie: lu=Rg3vHJZnehYLjVg7qi3bZjzg; Expires=Tue,15-Jan-2013 2 Set-Cookie: made_write_conn=1295214458; Path=/; Domain=.example.co Set-Cookie: reg_fb_gate=deleted; Expires=Thu, 01-Jan-1970 00:00:01 GM
- 90. Set-Cookie: lu=Rg3vHJZnehYLjVg7qi3bZjzg; Expires=Tue,15-Jan-2013 2 Set-Cookie: made_write_conn=1295214458; Path=/; Domain=.example.co Set-Cookie: reg_fb_gate=deleted; Expires=Thu, 01-Jan-1970 00:00:01 GM Persistent cookie
- 91. Set-Cookie: lu=Rg3vHJZnehYLjVg7qi3bZjzg; Expires=Tue,15-Jan-2013 2 Set-Cookie: made_write_conn=1295214458; Path=/; Domain=.example.co Set-Cookie: reg_fb_gate=deleted; Expires=Thu, 01-Jan-1970 00:00:01 GM
- 92. Set-Cookie: lu=Rg3vHJZnehYLjVg7qi3bZjzg; Expires=Tue,15-Jan-2013 2 Set-Cookie: made_write_conn=1295214458; Path=/; Domain=.example.co Set-Cookie: reg_fb_gate=deleted; Expires=Thu, 01-Jan-1970 00:00:01 GM
- 93.
- 94. Keep-Alive default HTTP whenkeep alive
- 95. HTTP 1.1 HTTP 1.0 Connection:Keep-Alive <not official> Keep-Alive: timeout=5, max=100 Connection: Keep-Alive
- 96.
- 97. Cache 종 도큐먼트들의 지속적인요청을 피하기 위해 클라이언트에 임시저
- 98.
- 99. For example… 왠만한 일아니면 바뀔일이 없음
- 100. Cache-Control: public, max-age=3600,must-revalidate Cache-Control: no-cache HTTP 1.1 HTTP 1.0 Expire: Thu, 01 Dec 1983 20:00:00 GMT Pragma: cache Pragma: no-cache
- 101. - Request headerHTTP1.1 General-header Request-header Entity-Header
- 102. - Request headerHTTP1.1 Cache control Check modified
- 103. - Request headerHTTP1.1 General-header Cahce-Control max-age=sec sec보다 오래된 데이터는 캐시하지 않음
- 104. - Request headerHTTP1.1 General-header Cahce-Control max-age=0 End-to-End revalidation 모든 프록시에 대해 재검증 요청
- 105. - Request headerHTTP1.1 Check modified If-Match If-None-Match 해당 e-tag가 있어야 진행이 됨 해당 e-tag가 존재하지 않아야 진행
- 106. - Request headerHTTP1.1 Check modified e-tag The ETag or entity tag is part of HTTP. It is one of several mechanisms that HTTP provides for web cache validation. It is provided by server.
- 107. - Request headerHTTP1.1 Check modified If-Match 해당 e-tag가 있어야 진행이 됨 412 (Precondition Failed) response Condition : - none of the entity tags match, - “*" is given and no current entity exists Ignore Condition : - any of the entity tags match - if the request results in anything other than a 2xx or 412 status (without If-M - if "*" is given and any current entity exists for the resource
- 108. - Request headerHTTP1.1 Check modified If-None-Match 해당 e-tag가 존재하지 않아야 진행 304 Not Modified Condition : - e tag is existed If-None-Match: * 304 Not Modified Condition : - if the resource is there and the other condition is met
- 109. If-Modified-Since: <date> - RequestheaderHTTP 1.1 Check modified 해당 날짜로 부터 변경 사항이 있는가 확인
- 110. - Response headerHTTP1.1 Cache control Checksum header
- 111. - Response headerHTTP1.1 Cache control Cache-Control: public, max-age=3600, must-revalidate Cache-Control: no-store Cache-Control: no-cache
- 112. - Response headerHTTP1.1 Cache control Cache-Control: public, max-age=3600, must-revalidate proxy-revalidateprivate 수명 재확인
- 113. Proxy Server Client cached cached -Response headerHTTP 1.1 Cache control In public
- 114. Proxy Server Client not-cached cached Inprivate - Response headerHTTP 1.1 Cache control
- 115. - Response headerHTTP1.1 Checksum header E-tag Last-Modified Expires Data 고유의 entity tag 최종 수정일 수명
- 116.
- 117.
- 118. The max-age directivetakes priority over Expires, so if max-age is present in a response, the calculation is simply: freshness_lifetime = max_age_value Otherwise, if Expires is present in the response, the calculation is: freshness_lifetime = expires_value - date_value
- 119.
- 120.
- 121. IF…. optical fiber 1sec = 7.5 revolution for half rev = 66ms
- 122.
- 123.
- 124.
- 125. - Berners-Lee firstproposed the "WorldWideWeb" project in 1989. - The first documented version of HTTP was HTTP V0.9 (1991). - Dave Raggett led the HTTP Working Group (HTTP WG) in 1995. - RFC 1945 officially introduced and recognized HTTP V1.0 in 1996. - The HTTP/1.1, RFC 2068 was officially released in January 1997
- 126.
- 127.
- 128. In now timegoogle
- 129. 엄청난 진보 = 전체페이지 사이즈 증
- 130. 훨씬 더 많은리소스로 구성되어 있다. 다수의 도메인을 사용한다. 과거에 비해 매우 동적으로 동작한다. 보안이 보다 중요한 이슈가 되었다. 헤더의 길이가 길어졌다.
- 131. 훨씬 더 많은리소스로 구성되어 있다. 다수의 도메인을 사용한다. 과거에 비해 매우 동적으로 동작한다. 보안이 보다 중요한 이슈가 되었다. 헤더의 길이가 길어졌다.
- 132.
- 133. Layers 항상 TLS 위에서동작 HTTP 헤더 압축 바이너리 프로토콜 Multiplexing 웹 사이트를 재작성할 필요 없음 Server Push
- 134. 항상 TLS 위에서동작 TLS(SSL)의 기본 탑재 서버 보안의 중요성 증가
- 135. HTTP 헤더 압축 기존encoding: gzip은 압축은 startline과 header는 압축을 안함.
- 136. Cookie와 User-agent의 길이증가, 같은 헤더의 지속적 요청..
- 137.
- 138. 바이너리 프로토콜 패킷의 사이즈를줄일 수 있음.
- 139.
- 140.
- 141.
- 142.
- 143. HTTP 프로토콜의 두번째 버전 SPDY에 기반하고 있으며, 국제 인터넷 표준화 기구(IETF)에서 개발되고 있다. HTTP/2
- 144. Spdy HTTP/2 TLS(SSL) Required.SSL Not Required. Fast Encrypted Connections. Faster Encrypted Connections. Single-Host Multiplexing. Multi-Host Multiplexing. Compression. Faster, More Secure Compression. Prioritization. Improved Prioritization.
- 145. The HTTP/2 specificationwas published as RFC 7540 in 14 May 2015.
- 146. IIS supports HTTP/2in Windows 10 beta NGINX plans to support HTTP/2 by the end of 2015 Apache SPDY via the mod_spdy module Server Compatibility Browser Chrome supports HTTP/2 by default (version 41) Firefox supports HTTP/2 enabled by default (version 36) IE supports HTTP/2 (version 11, but only for Windows 10 beta)
- 147.