[B! http] drumscoã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

drumsco id:drumsco

httpã«é–¢ã™ã‚‹drumscoã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (69)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

ã€Œwebã‚’æ”¯ãˆã‚‹æŠ€è¡“ã€ã‚’èªã‚“ã§èˆˆå‘³æ·±ã‹ã£ãŸç®‡æ‰€ã‚’ãƒ”ãƒƒã‚¯ã‚¢ãƒƒãƒ—
ã‚¨ãƒ³ã‚¸ãƒ‹ã‚¢ã¨ã—ã¦åƒãå§‹ã‚ã¦å°‘ã—çµŒã£ãŸé ƒã«ã€ã€ŒWebã‚’æ”¯ãˆã‚‹æŠ€è¡“ã€ã‚’èªã¿ã¾ã—ãŸã€‚ Webã®å…¥é–€æ›¸ã¨ã—ã¦ã¯2å†Šç›®ã ã£ãŸã®ã§ã™ãŒã€1å†Šç›®ã«ã¯æ›¸ã‹ã‚Œã¦ãŠã‚‰ãšã€ã‹ã¤æ¤œç´¢ã—ã¦ã‚‚ãªã‹ãªã‹ãƒªãƒ¼ãƒã—ãšã‚‰ãã†ãªé¢ç™½ã„å†…å®¹ãŒå¤šæ•°ã‚ã‚Šã¾ã—ãŸã®ã§ã€ãã‚Œã‚‰ã‚’ãƒ”ãƒƒã‚¯ã‚¢ãƒƒãƒ—ã—ã¦ã„ãã¾ã™^^ã€‚ SOAP å¯¾ REST Webã‚¢ãƒ¼ã‚ãƒ†ã‚¯ãƒãƒ£ã®æ¨™æº–åŒ–ã«ãŠã‘ã‚‹å¤§ããªè«–äº‰ RESTã®å°é å…ƒã€…ã¯å½“æ™‚ã‚«ãƒ«ãƒ•ã‚©ãƒ«ãƒ‹ã‚¢å¤§å¦ã®å¤§å¦é™¢ç”Ÿã ã£ãŸã‚‰äººãŒã€åˆ†æžã¨ç ”ç©¶ã‚’ã—ã¦ï¼‘ã¤ã®ã‚¢ãƒ¼ã‚ãƒ†ã‚¯ãƒãƒ£ã‚¹ã‚¿ã‚¤ãƒ«ã‚’RESTã‚’åä»˜ã‘ã¦è«–æ–‡ã¨ã—ã¦æå‡ºã—ãŸã®ãŒå§‹ã¾ã‚Šã€‚ RESTã®æå”±è€…ãŒå¤§ãƒ™ãƒ³ãƒ€ãƒ¼ãŒæŽ¨é€²ã™ã‚‹SOAPãƒ™ãƒ¼ã‚¹ã®æŠ€è¡“ã‚’å¦å®šã—ã€WebãŒWebã‚‰ã—ãã‚ã‚‹ãŸã‚ã®ã‚¢ãƒ¼ã‚ãƒ†ã‚¯ãƒãƒ£ã‚¹ã‚¿ã‚¤ãƒ«ã¨ã—ã¦RESTã‚’æŽ¨å¥¨ã™ã‚‹ãŒã€ä¸€äººã®ç ”ç©¶è€…ã¨å¤§æ‰‹ãƒ™ãƒ³ãƒ€ãƒ¼ã§ã¯æ”¿æ²»çš„ãªåŠ›ã®å·®ãŒæ´ç„¶ã¨ã—ã¦ã„ã¦ã€å£°ãŒå±Šã‹ãªã„ã€‚ RESTã®æ™®åŠã«å¼¾ã¿ã‚’ä»˜ã‘ãŸã®ã¯2002å¹´ã«ç™»å ´ã—ãŸAmazon Webã‚µãƒ¼
drumsco 2022/10/03
architecture

REST

SOAP

http
ãƒªãƒ³ã‚¯
https://jp.techcrunch.com/2021/06/02/quic-ietf-rfc-9000-http-3/
drumsco 2021/07/21
RFC

network

TCP

QUIC

http

HTTP3
ãƒªãƒ³ã‚¯
RFC 2818 - HTTP Over TLS æ—¥æœ¬èªžè¨³
RFC 2818 - HTTP Over TLS æ—¥æœ¬èªžè¨³ åŽŸæ–‡URL : https://datatracker.ietf.org/doc/html/rfc2818 ã‚¿ã‚¤ãƒˆãƒ« : RFC 2818 - HTTPã‚ªãƒ¼ãƒãƒ¼TLS ç¿»è¨³ç·¨é›† : è‡ªå‹•ç”Ÿæˆ [è¦ç´„] RFC 2818ã¯ã€HTTP Over TLSï¼ˆHTTPSï¼‰ã®ä»•æ§˜ã‚’å®šç¾©ã—ã¦ãŠã‚Šã€ã‚»ã‚ãƒ¥ã‚¢ãªé€šä¿¡ã‚’æä¾›ã™ã‚‹ãŸã‚ã«è¨è¨ˆã•ã‚Œã¦ã„ã¾ã™ã€‚ã“ã®RFCã®ç›®çš„ã¯ã€TLSã‚’ä½¿ç”¨ã—ã¦HTTPé€šä¿¡ã‚’æš—å·åŒ–ã—ã€èªè¨¼ã™ã‚‹ã“ã¨ã§ã€ãƒ‡ãƒ¼ã‚¿ã®æ©Ÿå¯†æ€§ã¨ä¿¡é ¼æ€§ã‚’ç¢ºä¿ã™ã‚‹ã“ã¨ã§ã™ã€‚ Network Working Group E. Rescorla Request for Comments: 2818 RTFM, Inc. Category: Informational May 2000
drumsco 2021/07/20
HTTP Over TLS æ—¥æœ¬èªžè¨³

RFC

RFC2818

http

TLS
ãƒªãƒ³ã‚¯
HTTP Over TLS
English HTTP ã‚ªãƒ¼ãƒãƒ¼ TLS (HTTP Over TLS) ã“ã®ãƒ¡ãƒ¢ã®ä½ç½®ä»˜ã‘ ã“ã®ãƒ¡ãƒ¢ã¯ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ã«æƒ…å ±æä¾›ã™ã‚‹ã‚‚ã®ã§ã™ã€‚ã“ã‚Œã¯ã€ã„ã‹ãªã‚‹ã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆæ¨™æº–ã‚’ã‚‚å®šã‚ã‚‹ã‚‚ã®ã§ã¯ã‚ã‚Šã¾ã›ã‚“ã€‚ã“ã®ãƒ¡ãƒ¢ã®é…å¸ƒã«ã¯åˆ¶é™ã¯ã‚ã‚Šã¾ã›ã‚“ã€‚ è‘—ä½œæ¨©è¡¨è¨˜ Copyright (C) The Internet Society (2000).Â All Rights Reserved. è¦æ—¨ ã“ã®ãƒ¡ãƒ¢ã¯ã€ã€Œã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆè¶Šã—ã® HTTP ã‚³ãƒã‚¯ã‚·ãƒ§ãƒ³ã‚’ã‚»ã‚ãƒ¥ã‚¢ã«ã™ã‚‹ãŸã‚ã® TLS ã®ä½¿ã„æ–¹ã€ã‚’è¨˜è¿°ã—ã¾ã™ã€‚ç¾åœ¨ã®å®Ÿè·µã¯ã€HTTP ã‚ªãƒ¼ãƒãƒ¼ SSLï¼ˆTLS ã®å‰èº«ï¼‰ã¨ã—ã€ç•°ãªã‚‹ã‚µãƒ¼ãƒãƒ¼ãƒãƒ¼ãƒˆã®åˆ©ç”¨ã«ã‚ˆã£ã¦ã€ã‚»ã‚ãƒ¥ã‚¢ã«ã•ã‚ŒãŸãƒˆãƒ©ãƒ•ã‚£ãƒƒã‚¯ã‚’ã‚»ã‚ãƒ¥ã‚¢ã§ãªã„ãƒˆãƒ©ãƒ•ã‚£ãƒƒã‚¯ã¨åŒºåˆ¥ã™ã‚‹ã‚‚ã®ã§ã™ã€‚æœ¬æ›¸ã¯ã€ãã®å®Ÿè·µã‚’ TLS ã‚’ä½¿ã£ã¦æ–‡æ›¸åŒ–ã—ã¾ã™ã€‚ä½µèªæ–‡æ›¸ã¯ã€é€šå¸¸ã® HTTP ã¨åŒä¸€ã®ãƒãƒ¼ãƒˆä¸Šã§ H
drumsco 2021/07/20
RFC2818 HTTP Over TLS ã®æ—¥æœ¬èªžè¨³

RFC

RFC2818

TLS

http
ãƒªãƒ³ã‚¯
HTTP â€” æ—¥æœ¬èªžè¨³
~HTTPã‚’å®šç¾©ã™ã‚‹å„ç¨®~æ–‡æ›¸ ~HTTPã¯ã€åˆ†æ•£åž‹ã®å”èª¿çš„ãª~hypertextæƒ…å ±~systemç”¨ã®ï¼Œ~statelessãªå¿œç”¨~levelã®~protocolã§ã‚ã‚‹ã€‚ â—Ž The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. ~HTTPã¯ã€ä»¥ä¸‹ã«æŒ™ã’ã‚‹ï¼» `~IETFï¼ https://ietf.org/$ ~RFC, `IANAï¼ https://www.iana.org/$ ~registry ï¼½ã«ã‚ˆã‚Šå®šç¾©ã•ã‚Œã‚‹ã€‚ â—Ž HTTP is defined by these IETF RFCs and IANA registries. ã€ ä»¥ä¸‹ã«ãŠã‘ã‚‹å„é …ã®å…ˆ
drumsco 2021/07/20
RFC

http

documentation
ãƒªãƒ³ã‚¯
ðŸ“„ HTTP Documentation
ðŸ“„ HTTP Documentation HTTP is defined by these IETF RFCs and IANA registries. Core Specifications The â€œcoreâ€ semantics of the HTTP protocol are defined by: RFC 9110: HTTP Semantics RFC 9111: HTTP Caching Those semantics are expressed â€œon the wireâ€ in three ways: RFC 9112: HTTP/1.1 RFC 9113: HTTP/2 RFC 9114: HTTP/3 Later versions of HTTP offer field compression: RFC 7541: HPACK Header Compression f
drumsco 2021/07/20
RFC

http

documentation
ãƒªãƒ³ã‚¯
HTTP/2æ™‚ä»£ã®ãƒ‰ãƒ¡ã‚¤ãƒ³ã‚·ãƒ£ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã‚’è€ƒãˆã‚‹ | TeraDasï¼ˆãƒ†ãƒ©ãƒ€ã‚¹ï¼‰
ã†ã¡ã®ã‚µã‚¤ãƒˆã¯ã€è¨˜äº‹ã‚„ã‚µã‚¤ãƒ‰ãƒãƒ¼ãªã©ã«ç”»åƒãŒå¤šã„ã¨ã„ã†ã“ã¨ã‚‚ã‚ã‚Šã€ã‚µã‚¤ãƒˆé«˜é€ŸåŒ–ã®ãŸã‚ã«ãƒ‰ãƒ¡ã‚¤ãƒ³ã‚·ãƒ£ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã¨ã„ã†æ‰‹æ³•ã‚’ä½¿ã£ã¦ã„ã¾ã™ãŒã€ä»Šå¾Œã€HTTP/2å¯¾å¿œã‚’è€ƒãˆãŸã¨ãã€ã“ã‚Œã‚’ã©ã†ã—ã¦ã‚†ã‘ã°è‰¯ã„ã®ã‹ã€å°‘ã—è€ƒãˆã¦ã¿ã¾ã—ãŸã€‚ ãƒ‰ãƒ¡ã‚¤ãƒ³ã‚·ãƒ£ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã¨ã„ã†ã®ã¯ã€HTML ã‚„ç”»åƒã€JavaScript ãªã©ã‚’è¤‡æ•°ãƒ‰ãƒ¡ã‚¤ãƒ³ã‹ã‚‰é…ä¿¡ã™ã‚‹é«˜é€ŸåŒ–æ‰‹æ³•ã§ã™ã€‚HTTP/1.x ã§ã¯ã€ãƒ–ãƒ©ã‚¦ã‚¶ãŒ1ãƒ‰ãƒ¡ã‚¤ãƒ³ã«åŒæ™‚ã«å¼µã‚Œã‚‹ã‚»ãƒƒã‚·ãƒ§ãƒ³æ•°ãŒå°‘ãªã„ãŸã‚ã€ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’è¤‡æ•°ãƒ‰ãƒ¡ã‚¤ãƒ³ã«åˆ†æ•£é…ç½®ã™ã‚‹ã“ã¨ã§ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã®ä¸¦åˆ—åº¦ã‚’ä¸Šã’ã€é«˜é€ŸåŒ–ã—ã‚ˆã†ã€‚ã¨ã„ã†ãƒ†ã‚¯ãƒ‹ãƒƒã‚¯ã«ãªã‚Šã¾ã™ã€‚ã¨ã„ã†ã‚ã‘ã§ã€ã†ã¡ã®å ´åˆã€3ãƒ‰ãƒ¡ã‚¤ãƒ³ã‹ã‚‰åˆ†å‰²é…ä¿¡ã—ã¦ã„ã‚‹çŠ¶æ³ã§ã™ã€‚ ã—ã‹ã—ã€HTTP/2 ã«ãªã‚‹ã¨ã€ã“ã®ã‚ãŸã‚Šã®äº‹æƒ…ãŒå¤§ããå¤‰ã‚ã‚Šã¾ã™ã€‚ã¨ã„ã†ã®ã¯ã€HTTP/2 ã§ã¯ã€1ã¤ã®TCPã‚»ãƒƒã‚·ãƒ§ãƒ³å†…ã§è¤‡æ•°ãƒªã‚½ãƒ¼ã‚¹ã‚’ä¸¦åˆ—ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã§ãã‚‹ã‚ˆã†ã«ãªã‚‹ã‹ã‚‰ã§ã™ã€‚ ã¤ã¾ã‚Š
drumsco 2020/08/14
[HTTP/2][parallel][Nginx][RFC]è¤‡æ•°ã®ãƒ‰ãƒ¡ã‚¤ãƒ³ãŒ1ã¤ã®IPã‚¢ãƒ‰ãƒ¬ã‚¹ã«è§£æ±ºã•ã‚Œã‚‹å ´åˆã€ HTTP/1.x ã¨ HTTP/2 ã«å¯¾å¿œã™ã‚‹ãƒ‰ãƒ¡ã‚¤ãƒ³ã‚·ãƒ£ãƒ¼ãƒ‡ã‚£ãƒ³ã‚°ã‚’å®Ÿç¾ã§ãã‚‹ã€‚

domain-shading

performance

http
ãƒªãƒ³ã‚¯
HTTPãƒ˜ãƒƒãƒ€ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚° Etagãƒ»Last-Modified | REDBOX Labo
ä»Šå›žã¯æ—¢ã«CDNã‚’åˆ©ç”¨ã—ã¦ã„ã‚‹æ–¹ã‚‚ã€åˆ©ç”¨ã—ã¦ã„ãªã„æ–¹ã‚‚ä»Šã™ãå‡ºæ¥ã‚‹HTTPãƒ˜ãƒƒãƒ€ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°ã‚’ã”ç´¹ä»‹ã—ã¾ã™ HTTPãƒ˜ãƒƒãƒ€ã®ãŠè©±ã§ã¯ã€ãƒ¬ã‚¹ãƒãƒ³ã‚¹ãƒ˜ãƒƒãƒ€ã‚„ãƒªã‚¯ã‚¨ã‚¹ãƒˆãƒ˜ãƒƒãƒ€ã®ä¸ã«ä½•ãŒã‚ã‚Šã€ã©ã†ã„ã†å½¹å‰²ãªã®ã‹ç°¡å˜ã«ã¾ã¨ã‚ã¦ã¿ã¾ã—ãŸãŒã€éžå¸¸ã«å¤šãã®ãƒ‡ãƒ¼ã‚¿ãŒWEBã®ã‚„ã‚Šã¨ã‚Šã§åˆ©ç”¨ã•ã‚Œã¦ã„ã‚‹ã“ã¨ãŒåˆ†ã‹ã£ãŸã¨æ€ã„ã¾ã™ã€‚ CDNåˆ©ç”¨æ™‚ã«åˆ©ç”¨è€…å´ãŒå‡ºæ¥ã‚‹ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°ã¯ã€ã‚ªãƒªã‚¸ãƒ³ã‚µãƒ¼ãƒãƒ¼å´ã®Apacheã‚„Nginxãªã©ã§ã©ã®ã‚ˆã†ãªHTTPãƒ¬ã‚¹ãƒãƒ³ã‚¹ãƒ˜ãƒƒãƒ€ã‚’ä»˜ä¸Žã™ã‚‹ã®ã‹ã€ã—ãªã„ã®ã‹ã¨ã„ã†ã“ã¨ã‚’æ±ºã‚ã‚‹ãƒ˜ãƒƒãƒ€ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°ã§ã™ã€‚ Last-Modifiedãƒ˜ãƒƒãƒ€ã¯ãƒ¬ã‚¹ãƒãƒ³ã‚¹ãƒ˜ãƒƒãƒ€ã®ã²ã¨ã¤ã§Apacheã‚„Nginxãªã©ã®WEBã‚µãƒ¼ãƒãƒ¼å´ã§é©åˆ‡ãªè¨å®šã‚’ã™ã‚‹ã“ã¨ã«ã‚ˆã£ã¦ã€ãƒ–ãƒ©ã‚¦ã‚¶å´ã«ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®æœ€çµ‚æ›´æ–°æ™‚åˆ»ã‚’é€ä¿¡ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ ãƒ–ãƒ©ã‚¦ã‚¶å´ã¯ã€ã“ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã®æœ€çµ‚æ›´æ–°æ™‚åˆ»ã‚’è¦šãˆã¦ãŠãæ¬¡å›žãƒªã‚¯ã‚¨ã‚¹ãƒˆã—ãŸéš›ã«ãƒªã‚¯ã‚¨ã‚¹ãƒˆãƒ˜ãƒƒ
drumsco 2020/01/09
ã‚ªãƒªã‚¸ãƒ³ã‚µãƒ¼ãƒãƒ¼ãŒè¤‡æ•°å°ã‚ã‚‹å ´åˆã«ã¯ã€ETag ãŒæ©Ÿèƒ½ã—ãªã„ã‹ã‚‚ã—ã‚Œãªã„ã€‚ä»˜ä¸Žã—ãªã„ã»ã†ãŒè‰¯ã„ã€‚

http

cache
ãƒªãƒ³ã‚¯
HTTP ã‚ãƒ£ãƒƒã‚·ãƒ¥ã‚’ä½¿ç”¨ã—ã¦ä¸è¦ãªãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ ãƒªã‚¯ã‚¨ã‚¹ãƒˆã‚’é˜²æ¢ã™ã‚‹ Â |Â Articles Â |Â web.dev
å¯¾å¿œãƒ–ãƒ©ã‚¦ã‚¶ <ph type="x-smartling-placeholder"></ph> 1 å€‹ <ph type="x-smartling-placeholder"></ph> 12 å€‹ <ph type="x-smartling-placeholder"></ph> 1 å€‹ <ph type="x-smartling-placeholder"></ph> 1 å€‹ ã‚½ãƒ¼ã‚¹ HTTP ã‚ãƒ£ãƒƒã‚·ãƒ¥ã®ä»•çµ„ã¿ ãƒ–ãƒ©ã‚¦ã‚¶ãŒå®Ÿè¡Œã™ã‚‹ã™ã¹ã¦ã® HTTP ãƒªã‚¯ã‚¨ã‚¹ãƒˆã¯ã€ã¾ãšãƒ–ãƒ©ã‚¦ã‚¶ ã‚ãƒ£ãƒƒã‚·ãƒ¥ã«ãƒ«ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã•ã‚Œã€ãƒªã‚¯ã‚¨ã‚¹ãƒˆã®å®Ÿè¡Œã«ä½¿ç”¨ã§ãã‚‹æœ‰åŠ¹ãªã‚ãƒ£ãƒƒã‚·ãƒ¥ ãƒ¬ã‚¹ãƒãƒ³ã‚¹ãŒã‚ã‚‹ã‹ã©ã†ã‹ãŒç¢ºèªã•ã‚Œã¾ã™ã€‚ä¸€è‡´ã™ã‚‹å ´åˆã€ãƒ¬ã‚¹ãƒãƒ³ã‚¹ãŒã‚ãƒ£ãƒƒã‚·ãƒ¥ã‹ã‚‰èªã¿å–ã‚‰ã‚Œã‚‹ãŸã‚ã€ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ ãƒ¬ã‚¤ãƒ†ãƒ³ã‚·ã¨è»¢é€ã«ã‚ˆã£ã¦ç™ºç”Ÿã™ã‚‹ãƒ‡ãƒ¼ã‚¿ã‚³ã‚¹ãƒˆã®ä¸¡æ–¹ã‚’æŽ’é™¤ã§ãã¾ã™ã€‚ HTTP ã‚ãƒ£ãƒƒã‚·ãƒ¥ã®å‹•ä½œã¯ã€ãƒªã‚¯ã‚¨ã‚¹ãƒˆ ãƒ˜ãƒƒãƒ€ãƒ¼ã¨ãƒ¬ã‚¹ãƒãƒ³ã‚¹
drumsco 2020/01/09
http

cache
ãƒªãƒ³ã‚¯
apache MPMè¨å®šã‚’è¦‹ç›´ã—ãŸã‚‰ã€CPUè² è·ãŒä¸‹ãŒã‚ŠWordPressãŒè»½ããªã£ãŸ | Check!Site
drumsco 2019/12/09
Apache 2.4 ã‹ã‚‰ã¯ event ãŒæ¨™æº–ã€‚

Apache

http

MPM

performance
ãƒªãƒ³ã‚¯
Check Apache Httpd MPM Config Limits | Surnia Ulula
A little while ago I had to reboot a clientâ€™s VM because the web server forked too many processes. They were making use of PHP, but the web server had not been configured for the resulting larger process size. I searched for a tool that would analyze the size of running httpd processes, and project the impact of starting the maximum number of processes allowed by MaxClients or ServerLimit, but did
drumsco 2019/12/09
check-httpd-limits.pl ã®ç´¹ä»‹è¨˜äº‹ã€‚

Apache

http

Perl
ãƒªãƒ³ã‚¯
Apache HTTP Server: MPMãƒ‘ãƒ©ãƒ¡ãƒ¼ã‚¿ ãƒãƒ¼ãƒˆã‚·ãƒ¼ãƒˆ
ã“ã‚“ã«ã¡ã¯æ»æ¾¤ã§ã™ã€‚ãŸã¾ã«ã¯apacheãƒã‚¿ã¨ã„ã†ã“ã¨ã§ä¸€ã¤ã€‚ Apache HTTP Serverã®ãƒ‘ãƒ©ãƒ¡ãƒ¼ã‚¿ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°ã§ã¯MaxClientsãªã©ã®MPMï¼ˆãƒžãƒ«ãƒ ãƒ—ãƒã‚»ãƒƒã‚·ãƒ³ã‚° ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ï¼‰é–¢é€£ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–ã®è¨å®šå€¤ã‚’èª¿æ•´ã™ã‚‹ã“ã¨ãŒå¤šã„ã§ã™ã€‚æœ¬è¨˜äº‹ã§ã¯MPMé–¢é€£ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–ã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã‚„ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–é–“ã®é–¢ä¿‚ã‚’è¡¨ã«ã¾ã¨ã‚ãŸã®ã§ç´¹ä»‹ã—ã¾ã™ã€‚ æ³¨æ„äº‹é … UNIXç³»OSã«ãŠã‘ã‚‹èª¬æ˜Žã¨ãªã‚Šã¾ã™ã€‚ãƒãƒ¼ã‚¸ãƒ§ãƒ³2.2ç³»ãŠã‚ˆã³2.4ç³»ã®ä¸¡æ–¹ã«ã¤ã„ã¦èª¬æ˜Žã—ã¾ã™ã€‚ é–¢ä¿‚å¼ã«ãŠã„ã¦ãƒãƒ¼ã‚¸ãƒ§ãƒ³2.4ç³»ã®å ´åˆã¯MaxClientsã‚’MaxRequestWorkersã«ç½®ãæ›ãˆã¦èªã‚“ã§ãã ã•ã„ã€‚ ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–åã«ã¯å…¬å¼ã‚µã‚¤ãƒˆã®ãƒªãƒ³ã‚¯ã‚’å¼µã£ã¦ã„ã¾ã™ã€‚å…¬å¼ã®èª¬æ˜Žã‚‚ç¢ºèªã—ã¦ãã ã•ã„ã€‚ ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆã®æ¬„ã§æ‹¬å¼§ä»˜ãã‚‚ã®ã¯ãã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–ãã®ã‚‚ã®ã¯è¨å®šä¸å¯ã§ã¯ã‚ã‚‹ãŒã€å†…éƒ¨çš„ã«è¨å®šã•ã‚Œã¦ã„ã‚‹ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã‚’ç¤ºã—ã¦ã„
drumsco 2019/12/09
Apache

http

MPM
ãƒªãƒ³ã‚¯
ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯è¶Šã—ã§ãƒ‘ã‚¤ãƒ—ã—ãŸã‚Šã€ã‚ã‚‰ã‚†ã‚‹ãƒ‡ãƒã‚¤ã‚¹é–“ã§ãƒ‡ãƒ¼ã‚¿è»¢é€ã—ãŸã„ï¼ - Qiita
ä½•ã‚’è§£æ±ºã—ãŸã„ã‹ï¼Ÿ Mac, Windows, Linux, iPhoneã‚„Androidã®ã‚¹ãƒžãƒ›ãƒ»ã‚¿ãƒ–ãƒ¬ãƒƒãƒˆã¨ã‹ã®ãƒ‡ãƒã‚¤ã‚¹é–“ã§ãƒ‡ãƒ¼ã‚¿ã®è»¢é€ã—ãŸã„ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ Slackã¨ã‹Lineã¨ã‹Skypeã¨ã‹AirDropã¨ã‹ã‚ã£ã¦ã‚‚ é€ã‚ŠãŸã„ç›¸æ‰‹ã¨å…±é€šã—ã¦ä½¿ã£ã¦ã„ã‚‹ã‚µãƒ¼ãƒ“ã‚¹ã‚’æŽ¢ã™å¿…è¦ã¨ã‹ã€ GUIã®ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ãŒå¿…è¦ã¨ã‹ã€ AirDropã ã¨Appleç³»OSã§ã‚ã‚‹å¿…è¦ ãŒã‚ã‚‹ãªã©ã®è»¢é€ã®éšœå£ãŒã‚ã£ã¦ã€GUIãŒä½¿ãˆãªã„ãƒ‡ãƒã‚¤ã‚¹ã«é€ã‚ŠãŸã„ã¨ããªã©ã¯å›°ã£ã¦ã—ã¾ã„ã¾ã™ã€‚ ã™ã§ã«ãŸãã•ã‚“ã®ãƒ•ã‚¡ã‚¤ãƒ«å…±æœ‰ç³»ã®ã‚µãƒ¼ãƒ“ã‚¹ãŒã‚ã‚Šã¾ã™ãŒã€ã‚³ãƒžãƒ³ãƒ‰ã‚’ä½¿ã£ãŸCUIãƒ™ãƒ¼ã‚¹ã«ã‚ã¾ã‚Šè¦ªåˆ‡ãªè¨è¨ˆãªã‚‚ã®ã¯ã‚ã¾ã‚Šãªã„ã¨æ€ã„ã¾ã™ã€‚ ãã“ã§ã€ä¸Šè¨˜ã®å•é¡Œã‚’è§£æ±ºã™ã‚‹ãŸã‚ã«ã€ä»¥ä¸‹ã®ã‚ˆã†ãªãƒ•ã‚¡ã‚¤ãƒ«è»¢é€ã®ä»•çµ„ã¿ã‚’ä½œã‚Šã¾ã—ãŸã€‚ ä»–ãƒ‡ãƒã‚¤ã‚¹é–“ã§ãƒ‡ãƒ¼ã‚¿è»¢é€ãŒã§ãã€ åˆ¥é€”ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ä¸è¦ã§ã€ ãƒ‘ã‚¤ãƒ—ã«ã¨ã¦ã‚‚è¦ªå’Œæ€§ãŒé«˜ãã‚¨ãƒ³
drumsco 2019/07/31
piping-server

node.js

pipe

stream

network

http

https
ãƒªãƒ³ã‚¯
è²¬ä»»ã‚ã‚‹é–‹ç™ºè€…ã®ãŸã‚ã®HTTPãƒ˜ãƒƒãƒ€ãƒ¼ | Yakst
å®‰å…¨ã§ã€èª°ã«ã‚‚æ‰‹é ƒã§ã‚¢ã‚¯ã‚»ã‚¹ã—ã‚„ã™ãã€ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’å°Šé‡ã—ãŸWebã‚’ä½œã‚‹ãŸã‚ã®HTTPãƒ˜ãƒƒãƒ€ãƒ¼ã®ãƒ—ãƒ©ã‚¯ãƒ†ã‚£ã‚¹ [UI/UX]åŽŸæ–‡ HTTP headers for the responsible developer - Twilio (English) åŽŸæ–‡è‘—è€… Stefan Judis åŽŸæ–‡å…¬é–‹æ—¥ 2019-04-23 ç¿»è¨³ä¾é ¼è€… ç¿»è¨³è€… meiq ç¿»è¨³ãƒ¬ãƒ“ãƒ¥ã‚¢ãƒ¼ doubl emarket msh5 åŽŸè‘—è€…ã¸ã®ç¿»è¨³å ±å‘Š 1950æ—¥å‰ ãƒ¡ãƒ¼ãƒ«ã§å ±å‘Šæ¸ˆã¿ ç·¨é›† This article was originally published on twilio.com, and translated with the permission of Twilio and the author. å½“è¨˜äº‹ã®åŽŸæ–‡ã¯twilio.comã«ã¦å…¬é–‹ã•ã‚ŒãŸã‚‚ã®ã§ã‚ã‚Šã€Twilioç¤¾ãŠã‚ˆã³åŽŸè‘—è€…ã®è¨±å¯ã‚’å¾—ã¦ç¿»è¨³ã—ã¦ã„ã¾ã™
drumsco 2019/07/12
http

security

CSP
ãƒªãƒ³ã‚¯
Apache 2.2 ã® internal dummy connection ã®è¬Ž - daily dayflower
ab ã§ãƒ‘ãƒ•ã‚©ãƒ¼ãƒžãƒ³ã‚¹ãƒ†ã‚¹ãƒˆã‚’è¡Œã£ã¦ã„ãŸã‚“ã§ã™ãŒï¼Œãƒã‚°ã« GET / HTTP/1.0" 200 643 "-" "Apache/2.2 (internal dummy connection)ã¿ãŸã„ãªã®ãŒãŸã¾ã«å‡ºç¾ã—ã¦ã¾ã—ãŸã€‚prefork mpm ã‚’ä½¿ã£ã¦ã„ã‚‹ã‚“ã§ã™ãŒï¼Œ MaxRequestsPerChild ã§ãƒ—ãƒã‚»ã‚¹ãŒå†ç”Ÿæˆã•ã‚Œã‚‹ã‚ãŸã‚Šã®ã‚¿ã‚¤ãƒŸãƒ³ã‚°ã§ã™ã‹ãï¼ˆé•ã†ã‹ã‚‚ï¼‰ã€‚è¨€åŠã•ã‚Œã¦ã„ã‚‹ãƒšãƒ¼ã‚¸ãŒã‚ã¾ã‚Šãªã„ã®ã§è¬Žã®ã¾ã¾ã§ã™ã€‚ä¸€å¿œå®Ÿå®³ã¯ãªã„ã‚‰ã—ã„ã§ã™ãŒã€‚ è¿½è¨˜ 2006å¹´07æœˆ28æ—¥ id:naoya [apache] åŒã˜ãè¬Žã€‚mod_proxy_balancer ã® live check ç”¨ãƒªã‚¯ã‚¨ã‚¹ãƒˆã‹ãªã¨æ€ã£ã¦ãŸã‚“ã ã‘ã©ã€‚ ã‚ãƒ¼ï¼Œãã†ã„ãˆã° mod_proxy ä½¿ã£ã¦ã¾ã—ãŸã€‚ã§ã‚‚å®Ÿéš›ã©ã†ãªã‚“ã ã‚ã€‚ã¨ã„ã†ã“ã¨ã§ï¼Œä»Šæ—¥ãƒžã‚¹ã‚¿ãƒ¼ã‚¢ãƒƒãƒ—ã‚’çµ‚ãˆã¦ã¡ã‚‡ã„æš‡ã«ãªã£ãŸã®ã§ã‚½ãƒ¼ã‚¹ã‚’è¿½ã„ã‹ã‘ã¦ã¿ã¾ã—ãŸã€‚
drumsco 2019/04/26
graceful-stop ã®ãŸã‚ã«å®Ÿè£…ã•ã‚ŒãŸæ©Ÿæ§‹ã‚‰ã—ã„ã€‚

Apache

http
ãƒªãƒ³ã‚¯
Mapping Custom Domains Â |Â App Engine standard environment for Java Â |Â Google Cloud
Mapping Custom Domains Stay organized with collections Save and categorize content based on your preferences. You can use a custom domain rather than the default address that App Engine provides for your app. To use a custom domain, map the domain to your app, then update your DNS records. You can map a naked domain, such as example.com or a subdomain, such as subdomain.example.com. You can also u
drumsco 2018/11/06
HSTSã‚’ä½¿ç”¨ã™ã‚‹ãŸã‚ã«ã¯ã€Googleã¸é€£çµ¡ã—ã¦ Whitelist ã¸ç™»éŒ²ã—ã¦ã‚‚ã‚‰ã†å¿…è¦ãŒã‚ã‚‹ã€‚

Google

AppEngine

cloud

security

http

SSL

HSTS
ãƒªãƒ³ã‚¯
HTTP ã‚ãƒ£ãƒƒã‚·ãƒ¥ - HTTP | MDN
HTTP ã‚¬ã‚¤ãƒ‰ HTTP ã®æ¦‚è¦ å…¸åž‹çš„ãª HTTP ã‚»ãƒƒã‚·ãƒ§ãƒ³ HTTP ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ MIME ã‚¿ã‚¤ãƒ—ï¼ˆIANA ãƒ¡ãƒ‡ã‚£ã‚¢ç¨®åˆ¥ï¼‰ HTTP ã®åœ§ç¸® HTTP ã‚ãƒ£ãƒƒã‚·ãƒ¥ HTTP èªè¨¼ HTTP Cookie ã®ä½¿ç”¨ HTTP ã®ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆ HTTP æ¡ä»¶ä»˜ããƒªã‚¯ã‚¨ã‚¹ãƒˆ HTTP ç¯„å›²ãƒªã‚¯ã‚¨ã‚¹ãƒˆ ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ãƒã‚´ã‚·ã‚¨ãƒ¼ã‚·ãƒ§ãƒ³ HTTP/1.x ã®ã‚³ãƒã‚¯ã‚·ãƒ§ãƒ³ç®¡ç† HTTP ã®é€²åŒ– ãƒ—ãƒãƒˆã‚³ãƒ«ã®ã‚¢ãƒƒãƒ—ã‚°ãƒ¬ãƒ¼ãƒ‰ã®ä»•çµ„ã¿ ãƒ—ãƒã‚ã‚·ã‚µãƒ¼ãƒãƒ¼ã¨ãƒˆãƒ³ãƒãƒªãƒ³ã‚° HTTP ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆãƒ’ãƒ³ãƒˆ HTTP ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£ ã‚µã‚¤ãƒˆã®å®‰å…¨åŒ– HTTP Observatory Permissions Policy ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£ãƒãƒªã‚·ãƒ¼ (CSP) ã‚ªãƒªã‚¸ãƒ³é–“ãƒªã‚½ãƒ¼ã‚¹å…±æœ‰ (CORS) Cross-Origin Resource Policy (CORP) Strict-Transport-Securit
drumsco 2018/10/19
http

cache
ãƒªãƒ³ã‚¯
Should one call .close() on HttpServletResponse.getOutputStream()/.getWriter()?
In Java Servlets, one can access the response body via response.getOutputStream() or response.getWriter(). Should one call .close() on this OutputStream after it has been written to? On the one hand, there is the Blochian exhortation to always close OutputStreams. On the other hand, I don't think that in this case there is an underlying resource that needs to be closed. The opening/closing of sock
drumsco 2018/10/17
ServletRequest ã‹ã‚‰å–å¾—ã§ãã‚‹ Writer/OutputStream ãªã©ã® close ã¯ã€ã‚³ãƒ³ãƒ†ãƒŠã«ä»»ã›ã‚‹ã¹ã—ã€‚

Java

http
ãƒªãƒ³ã‚¯
S3ã®Content-Dispositionã®ãƒ–ãƒ©ã‚¦ã‚¶å¯¾å¿œã«ã¤ã„ã¦èª¿æŸ»ã—ã¦ã¿ãŸ - Innovator Japan Engineersâ€™ Blog
ã“ã‚“ã«ã¡ã¯ã€@gorou_178ã§ã™ã€‚ ä¸»ã«tenpu ã®é–‹ç™ºã‚’æ‹…å½“ã—ã¦ã„ã¾ã™ã€‚ tenpuã¯AWSã‚’åˆ©ç”¨ã—ã¦æ§‹ç¯‰ã—ã¦ãŠã‚Šã€ç‰¹ã«S3ã‚’ã‚ˆãä½¿ã†ã®ã§S3ã«ã¤ã„ã¦æ›¸ã“ã†ã¨æ€ã„ã¾ã™ã€‚ ãƒ¦ãƒ¼ã‚¶ã«ã‚µãƒ¼ãƒ“ã‚¹å´ã§æŒ‡å®šã—ãŸãƒ•ã‚¡ã‚¤ãƒ«åã§ãƒ•ã‚¡ã‚¤ãƒ«ã‚’ãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã•ã›ãŸã„å ´åˆã€ Content-Disposition ãƒ˜ãƒƒãƒ€ãƒ¼ã§ãƒ•ã‚¡ã‚¤ãƒ«åã‚’æŒ‡å®šã—ã¾ã™*1 ã—ã‹ã—ã€Content-Dispositionã®attachmentæŒ‡å®šã¯ãƒ–ãƒ©ã‚¦ã‚¶ã«ã‚ˆã£ã¦å¯¾å¿œçŠ¶æ³ãŒãƒãƒ©ãƒãƒ©ã§å¯¾å¿œã«è‹¦ã—ã‚“ã æ–¹ã‚‚å¤šã„ã‹ã¨æ€ã„ã¾ã™ã€‚S3ã«å¯¾ã—ã¦ãƒ•ã‚¡ã‚¤ãƒ«åæŒ‡å®šãƒ€ã‚¦ãƒ³ãƒãƒ¼ãƒ‰ã•ã›ã‚‹ã«ã¯ã€S3ã«Content-Dispositionã‚’æŒ‡å®šã™ã‚‹ã®ã§ã™ãŒã€ã‚¨ãƒ³ã‚³ãƒ¼ãƒ‰æ–¹æ³•ã«ã‚ˆã£ã¦ã¯ã‚¨ãƒ©ãƒ¼ã«ãªã£ãŸã‚Šã—ãŸãŸã‚ã€S3å´ã®å¯¾å¿œçŠ¶æ³ã‚’èª¿æŸ»ã—ã¦ã¿ã¾ã—ãŸã€‚ çµè«– æœ€æ–°ã®ãƒ–ãƒ©ã‚¦ã‚¶ã§ã¯ã€ S3ã«å¯¾ã—ã¦ Content-Dispositionã®filenameã‚’ RFC 5987
drumsco 2017/02/24
http

content-disposition

RFC5987
ãƒªãƒ³ã‚¯
H2O the optimized HTTP/1.x, HTTP/2 server
H2O is a new generation HTTP server that provides quicker response to users with less CPU, memory bandwidth utilization when compared to older generation of web servers. Designed from ground-up, the server implements of HTTP/2 and HTTP/3 taking the advantages of features including new and old content prioritization schemes, server push, 103 Early Hints, promising outstanding experience to the visi
drumsco 2016/06/24
http

http2

h2o

web-server
ãƒªãƒ³ã‚¯
1 2 3 4 æ¬¡ã®ãƒšãƒ¼ã‚¸