RFC 1958: Architectural Principles of the Internet
This RFC was published on the Internet Architecture Board (IAB) stream. This RFC is not endorsed by the IETF and has no formal standing in the IETF standards process. Network Working Group B. Carpenter, Editor Request for Comments: 1958 IAB Category: Informational June 1996 Architectural Principles of the Internet Status of This Memo This memo provides information for the Internet community. This
HTTP APIã®è©³ç´°ãªã‚¨ãƒ©ãƒ¼æƒ…å ±ã‚’ãƒ¬ã‚¹ãƒãƒ³ã‚¹ã«æŒãŸã›ã‚‹ãŸã‚ã®ä»•æ§˜
今日ã§ã¯ HTTP(s) 㧠API ãŒå…¬é–‹ã•ã‚Œã‚‹ã“ã¨ã¯å½“ãŸã‚Šå‰ã®æ™‚代ã§ã™ãŒã€ã‚¨ãƒ©ãƒ¼ã‚’アプリケーションã«ã©ã†ä¼ãˆã‚‹ã‹ã¯ã€å€‹ã€…ã® API ã®è¨è¨ˆã«ä¾å˜ã—ã¦ã„ã¾ã—ãŸã€‚特ã«ã€HTTP ステータスコードã¯æœ‰é™ã§ã‚ã‚Šã€å…ƒã€…æŒã£ã¦ã„ã‚‹æ„味ãŒã‚ã‚‹ã®ã§ã€è‡ªç”±ã«ä½¿ã†ã“ã¨ã¯ã§ãã¾ã›ã‚“。API ã¯ãã®ãƒ‰ãƒ¡ã‚¤ãƒ³ã”ã¨ã«ã‚‚ã£ã¨è¤‡é›‘ã§ç´°ã‹ãªã‚¨ãƒ©ãƒ¼æƒ…å ±ãŒã‚ã‚‹ã¯ãšã§ã€ãれらã¯ãƒ¬ã‚¹ãƒãƒ³ã‚¹ãƒœãƒ‡ã‚£ã«è¼‰ã›ã¦ã‚¢ãƒ—リケーションã«ä¼ãˆã‚‹ã“ã¨ã«ãªã‚Šã¾ã™ãŒã€ãã®æ›¸å¼ã«è¦å®šã¯ä»Šã¾ã§ã‚ã‚Šã¾ã›ã‚“ã§ã—ãŸã€‚ HTTP API ã«ã¦ã€ã‚¢ãƒ—リケーションã«ã‚¨ãƒ©ãƒ¼æƒ…å ±ã‚’ä¼é”ã™ã‚‹ãŸã‚ã®ï¼ˆãƒ¬ã‚¹ãƒãƒ³ã‚¹ãƒœãƒ‡ã‚£ã«è¼‰ã›ã‚‰ã‚Œã‚‹ï¼‰æ¨™æº–çš„ãªå½¢å¼ãŒã€RFC7807 Problem Details for HTTP APIs ã§å®šã‚られã¦ã„ã¾ã™ã€‚é©ç”¨ä¾‹ã¨ã—ã¦ã¯ã€ä»¥ä¸‹ã®ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚ HTTP/1.1 403 Forbidden Content-Type: application
RFC 7763: The text/markdown Media Type
Internet Engineering Task Force (IETF) S. Leonard Request for Comments: 7763 Penango, Inc. Category: Informational March 2016 ISSN: 2070-1721 The text/markdown Media Type Abstract This document registers the text/markdown media type for use with Markdown, a family of plain-text formatting syntaxes that optionally can be converted to formal markup languages such as HTML. Status of This Memo This do
RFC 1982: Serial Number Arithmetic
Network Working Group R. Elz Request for Comments: 1982 University of Melbourne Updates: 1034, 1035 R. Bush Category: Standards Track RGnet, Inc. August 1996 Serial Number Arithmetic Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Intern
HTTP/1.1 just got a major update.
The IETF just published several new RFCs that update HTTP/1.1: RFC 7230: Message Syntax and Routing RFC 7231: Semantics and Content RFC 7232: Conditional Requests RFC 7233: Range Request RFC 7234: Caching RFC 7235: Authentication RFC 7236: Authentication Scheme Registrations RFC 7237: Method Registrations RFC 7238: the 308 status code RFC 7239: Forwarded HTTP extension These documents make the ori
WebSocket(RFC 6455)上ã§ä½¿ç”¨ã™ã‚‹ãƒ—ãƒãƒˆã‚³ãƒ«è¨è¨ˆã«ã¤ã„ã¦ã®å‚™å¿˜éŒ² - kazuhoã®ãƒ¡ãƒ¢ç½®ãå ´
一般論ã¨ã—ã¦ã€å…¨äºŒé‡ã®é€šä¿¡ãƒ—ãƒãƒˆã‚³ãƒ«ã‚’実装ã™ã‚‹ã«ã‚ãŸã£ã¦ã¯ã€ã„ãã¤ã‹æ³¨æ„ã™ã¹ã点ãŒã‚ã£ã¦ã€å…·ä½“çš„ã«ã¯ã€åˆ°é”確èªã¨åˆ‡æ–シーケンスã«ã¤ã„ã¦å®šã‚ã¦ãŠã‹ãªã„ã¨ã€é€é”ã•ã‚ŒãŸã¯ãšã®ãƒ¡ãƒƒã‚»ãƒ¼ã‚¸ãŒãƒã‚¹ãƒˆã—ã¦ã„ãŸã‚Šã€åˆ‡æ–タイミングã«ã‚ˆã£ã¦ã‚¨ãƒ©ãƒ¼ãŒç™ºç”Ÿ*1ã—ãŸã‚Šã™ã‚‹ã€‚ 具体例をã‚ã’ã‚‹ã¨ã€ãŸã¨ãˆã°TCP/IPã«ãŠã„ã¦shutdown(2)を用ã„ãšã«ã€ã„ããªã‚Šclose(2)を呼んã§ã„ã‚‹ã¨ã€read(2)ã‚„write(2)ãŒã‚¨ãƒ©ãƒ¼(ECONNRESET)ã‚’è¿”ã™å ´åˆãŒã‚る。 ç¿»ã£ã¦ã€WebSocket (RFC6455)ã®å ´åˆã¯ã©ã†ãªã£ã¦ã‚‹ã‹ï¼Ÿã€€ã ã„ãŸã„以下ã®ã‚ˆã†ãªæ„Ÿã˜ã£ã½ã„。 ws.close()ãŒå‘¼ã³å‡ºã•ã‚Œã‚‹ã¨WebSocketã‚’CLOSING状態ã«å¤‰æ›´ã—ã€Closeフレームをé€ä¿¡ã™ã‚‹ ws.onmessageã¯WebCosketãŒCLOSING状態ã«ã‚る間も呼ã°ã‚Œã‚‹ã‹ã‚‚ã—ã‚Œãªã„*2 相手ã‹ã‚‰Closeフレーãƒ
RFC 3176: InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks
This RFC was published on the Legacy stream. This RFC is not endorsed by the IETF and has no formal standing in the IETF standards process. Network Working Group P. Phaal Request for Comments: 3176 S. Panchen Category: Informational N. McKee InMon Corp. September 2001 InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks Status of this Memo This memo provides i
YappoLogs: HTTP::AcceptLanguage - Accept-Language ヘッダを解æžã—ã¦é©åˆ‡ãªè¨€èªžã‚’è¿”ã™å›
HTTP::AcceptLanguage - Accept-Language ヘッダを解æžã—ã¦é©åˆ‡ãªè¨€èªžã‚’è¿”ã™å› 月曜日ã®æ‚ªé”ã“㨠yappo ã§ã™ã€‚ 今時ã®ã‚°ãƒãƒ¼ãƒãƒ«ãªç¤¾ä¼šã§ã¯ã¿ãªã•ã‚“多言語対応㮠web アプリを書ã„ã¦ã„ã‚‹ã¨ãŠã‚‚ã„ã¾ã™ãŒã€ãã®æ™‚ã«ä½¿ã† Accept-Language を解æžã—ã¦ãれるã®ã‚’書ãã¾ã—ãŸã€‚ HTTP::AcceptLanguage Plack ãªã‚¢ãƒ—リã ã£ãŸã‚‰ã€‚ my $lang = HTTP::AcceptLanguage->new($req->header('Accept-Language'))->match(qw/ en fr es ja zh-tw /);ã£ã¦ã™ã‚‹ã ã‘ã§ã€è‹±èªžãƒ•ãƒ©ãƒ³ã‚¹èªžã‚¹ãƒšã‚¤ãƒ³èªžæ—¥æœ¬èªžå°æ¹¾èªžã®ä¸ã‹ã‚‰ãƒ¦ãƒ¼ã‚¶ãŒåˆ©ç”¨å¯èƒ½ãªæœ€é©ãªè¨€èªžã‚’探ã—ã¦è¿”ã—ã¦ãã‚Œã¾ã™ã€‚ ã‚‚ã—é©åˆ‡ãªè¨€èªžãŒç„¡ã‘れ㰠undef ã‚’è¿”ã™ã®ã§ã€ã‚ãªãŸãŒãŠã™ã™ã‚ã®è¨€èªžã§è¿”ã—ã¦ãŠãã¨
IPv6アドレスã®:ã§åŒºåˆ‡ã‚‰ã‚ŒãŸéƒ¨åˆ†ã‚’何ã¦å‘¼ã¹ã°ã„ã„ã®ï¼Ÿ - yuyarinã®æ—¥è¨˜
IPv6アドレスã«ãŠã„ã¦:(コãƒãƒ³)ã§åŒºåˆ‡ã‚‰ã‚Œã‚‹2ãƒã‚¤ãƒˆã®éƒ¨åˆ†ã‚’何ã¦å‘¼ã¹ã°ã„ã„ã®ã ã‚ã†ã‹ï¼ŸIPv4アドレスã§ã¯ã‚ªã‚¯ãƒ†ãƒƒãƒˆ(octet)ã¨å‘¼ã°ã‚Œã¦ã„ã¦ã€ä¼šè©±ã®ä¸ã§ã€Œç¬¬4オクテットãŒã€œã€ã¿ãŸã„ãªä½¿ã„方をã™ã‚‹ã®ã ã‘ã©ã€IPv6アドレスã§ã€Œç¬¬3***ãŒã€œã€ã¿ãŸã„ãªè¡¨ç¾ã‚’ã—ãŸã„時ã«ä½•ã¦å‘¼ã¹ã°ã„ã„ã®ã ã‚ã†ã‹ï¼Ÿèª¿ã¹ã¦ã¿ãŸã€‚ 紹介ã™ã‚‹ã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆãƒ‰ãƒ©ãƒ•ãƒˆã§ã¯hextetã¨ã„ã†å˜èªžãŒæ案ã•ã‚Œã¦ã„ã¦ã€NANOGã§ã®ä¸€å®šã®æ”¯æŒã‚‚ã‚ã‚Šã€å€‹äººçš„ã«ã‚‚良ã•ã’ã ã£ãŸã®ã§ã“ã‚Œã‹ã‚‰ã¯hextetã£ã¦å‘¼ã‚“ã§ã„ã“ã†ã¨æ€ã†ã€‚ draft-denog-v6ops-addresspartnaming-04 draft-denog-v6ops-addresspartnaming-04ã§æ案ã•ã‚Œã¦ã„る呼ã³æ–¹ã¯ï¼’種類ã‚る。ãŸã ã—ã“ã®ãƒ‰ãƒ©ãƒ•ãƒˆã¯2011å¹´ã«Expireã—ã¦ãŠã‚Šã€RFCã«ã‚‚ãªã£ã¦ã„ãªã„。NANOGã®MLã§æŠ•ç¥¨ãªã©ã‚‚è¡Œã‚ã‚Œã¦ã€ã“
HTTP/1.1: Connections
part of Hypertext Transfer Protocol -- HTTP/1.1 RFC 2616 Fielding, et al. 8 Connections 8.1 Persistent Connections 8.1.1 Purpose Prior to persistent connections, a separate TCP connection was established to fetch each URL, increasing the load on HTTP servers and causing congestion on the Internet. The use of inline images and other associated data often require a client to make multiple requests o
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}