HTTPie – API testing client that flows with youIf you're in need of a great CLI tool to use with HTTP servers, RESTful APIs, and web services you're in luck. HTTPie from @jakubroztocil is the perfect solution 🤗 Part of December's #GHReleaseRadar https://httpie.org
ブラウザ開発者ツールã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¿ãƒ–ã«è¡¨ç¤ºã•ã‚Œãªã„æƒ…å ±é€ä¿¡æ‰‹æ³• - Qiita
ã¯ã˜ã‚ã« ã¯ã˜ã‚ã¾ã—ã¦ã€ã‚»ã‚ュリティエンジニアã®Satoki (@satoki00) ã§ã™ã€‚今回ã¯ãƒ–ラウザã®é–‹ç™ºè€…ツールã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¿ãƒ–ã‹ã‚‰éš ã‚Œã¦ã€Webサイト内ã®æƒ…å ±ã‚’é€ä¿¡ã™ã‚‹æ‰‹æ³•ã‚’ã¾ã¨ã‚ã¾ã™ã€‚所謂Exfiltrationã¨ã„ã†ã‚„ã¤ã§ã™ã€‚ä¸ã«ã¯CSPã®åˆ¶é™ã‚’Bypassã™ã‚‹ãŸã‚ã«ç”¨ã„られるテクニックもã‚ã‚Šã¾ã™ã€‚CTFãªã©ã§å®‰å…¨ã«ä½¿ã£ã¦ãã ã•ã„。 å‰æ 発端ã¯Web上ã§ãƒ†ã‚ストã®æ–‡å—数をカウントã§ãるサイトãŒé–‰éŽ–ã™ã‚‹éš›ã®è©±ã§ã™ã€‚カウント対象ã®ãƒ†ã‚ストデータãŒã‚µã‚¤ãƒˆé‹å–¶ (やサイトを改竄ã—ãŸæ”»æ’ƒè€…) ã«ç›—ã¿å–られã¦ã„ãªã„ã‹ã¨ã„ã†è°è«–ãŒå·»ãèµ·ã“ã£ã¦ã„ã¾ã—ãŸã€‚「盗ã¿å–られã¦ã„ãªã„ã€å´ã®ä¸»å¼µã¯ã€ãƒ–ラウザã®é–‹ç™ºè€…ツールã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¿ãƒ–ã«ãƒªã‚¯ã‚¨ã‚¹ãƒˆã‚’é€ä¿¡ã—ãŸå½¢è·¡ãŒãªã„ã¨ã„ã†ã‚‚ã®ã§ã—ãŸã€‚ã“ã“㧠ブラウザã®é–‹ç™ºè€…ツールã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã‚¿ãƒ–ã«è¡¨ç¤ºãŒãªã‘ã‚Œã°å¤–部ã¸ãƒ‡ãƒ¼ã‚¿ã‚’é€ä¿¡ã—ã¦ã„ãªã„ã®ã‹ï¼Ÿ ã¨ã„ã£ãŸç–‘å•ãŒ
The History of the URL | The Cloudflare Blog
On the 11th of January 1982 twenty-two computer scientists met to discuss an issue with ‘computer mail’ (now known as email). Attendees included the guy who would create Sun Microsystems, the guy who made Zork, the NTP guy, and the guy who convinced the government to pay for Unix. The problem was simple: there were 455 hosts on the ARPANET and the situation was getting out of control. This issue w
Cookie2 ã¨ã¯ä½•ã‹ | blog.jxck.io
Intro タイトルを見ã¦ã€ŒCookie ã®æ–°ã—ã„仕様ã‹ã€ã‚ャッãƒã‚¢ãƒƒãƒ—ã—よã†ã€ã¨æ€ã£ã¦é–‹ã„ãŸã®ãªã‚‰ã€ä»¥é™ã‚’èªã‚€å¿…è¦ã¯ãªã„。 Cookie History 2000 å¹´ã«ç™ºè¡Œã•ã‚ŒãŸ Cookie ã®ä»•æ§˜ã§ã‚ã‚‹ RFC 2965 ã§ã¯ã€ä»•æ§˜ä¸ã« Set-Cookie2/Cookie2 (以下 Cookie2) ã¨ã„ㆠ2 ã¤ã®ãƒ˜ãƒƒãƒ€ãŒå®šç¾©ã•ã‚Œã¦ã„る。ã—ã‹ã— 2011 å¹´ã«æ”¹å®šã•ã‚ŒãŸç¾è¡Œã® RFC 6265 ã§ã¯ãれらヘッダ㯠deprecate ã•ã‚Œã¦ãŠã‚Šã€å®Ÿéš›ã® Web ã§ã“れらã®ãƒ˜ãƒƒãƒ€ãŒäº¤æ›ã•ã‚Œã‚‹å ´é¢ã‚’ã€å°‘ãªãã¨ã‚‚ç†è€…ã¯è¦‹ãŸã“ã¨ãŒãªã„。å˜åœ¨ã™ã‚‰çŸ¥ã‚‰ãªã„開発者も多ã„ã ã‚ã†ã€‚ ç†è€…ã¯ãšã£ã¨ã€ã“ã®ä»•æ§˜ãŒã©ã®ã‚ˆã†ã«å‡ºã¦ãã¦ã€ã©ã†ã—ã¦æ¶ˆãˆã¦ã„ã£ãŸã®ã‹ãŒæ°—ã«ãªã£ã¦ã„ãŸã€‚ Web 上ã«ã‚‚æƒ…å ±ãŒå°‘ãªãã€ã€Œæ´å²ä¸Šã®ç†ç”±ã§ã€ã¨ã‹åˆ†ã‹ã£ãŸã‚ˆã†ãªã“ã¨ã‚’言ã£ã¦ã‚‹äººãŒãŸã¾ã«ã„ã‚‹ãらã„ã 。四åŠä¸–ç´€å‰ã®ã“ã¨ãªã®ã§çµŒç·¯ã‚’
Desktop & Web app – HTTPie
All the user-friendliness of our Terminal version, now wrapped up in a sleek graphical interface. Interact painlessly with APIsLeverage the power of AI-assisted workOrganize your work in spaces, collections, and tabsParametrize requests with variables and environmentsWork across devices with auto-save and realtime syncBuild and preview requests without sending themUse the app offline and without a
The HTTP QUERY Method
Groups By area/parent Apps & Realtime General Internet Ops & Management Routing Security Web and Internet Transport IAB IRTF IETF LLC RFC Editor Other Active AGs Active Areas Active Directorates Active IAB Workshops Active Programs Active RAGs Active Teams New work Chartering groups BOFs BOF Requests Other groups Concluded groups Non-WG lists Documents Search Recent I-Ds I-D submission IESG dashbo
The state of HTTP in 2022
At over thirty years old, HTTP is still the foundation of the web and one of the Internet’s most popular protocols—not just for browsing, watching videos and listening to music, but also for apps, machine-to-machine communication, and even as a basis for building other protocols, forming what some refer to as a “second waist†in the classic Internet hourglass diagram. What makes HTTP so successful
HTTP/Tokyo #1ã«è¡Œã£ã¦ã㟠- dackdive's blog
è¡Œã£ã¦ãã¾ã—ãŸã€‚ ä¸èº«ã®æ¿ƒã„勉強会ã§éžå¸¸ã«å‹‰å¼·ã«ãªã£ãŸã€‚ jxckã•ã‚“ã®ç™ºè¡¨ã¯åœ§å·»ã§ã—ãŸã€‚ Response Status codes 3xx @haormauyraa 資料: https://slides.araya.dev/http-tokyo-1/#slide=1 demo: https://playground.araya.dev/http-redirections/ 3xxç³»ã®ã‚¹ãƒ†ãƒ¼ã‚¿ã‚¹ã‚³ãƒ¼ãƒ‰ã®è©± 300〜308ã¾ã§ RFC7231, 7232, 7538 301, 302ã¯HTTP/1.0 300 Multiple Choices 対象ã®ãƒªã‚½ãƒ¼ã‚¹ãŒè¤‡æ•°ã®è¡¨ç¾ã‚’も㤠サーãƒãƒ¼ã¯ãƒªãƒ€ã‚¤ãƒ¬ã‚¯ãƒˆå…ˆã¨ã—ã¦è¤‡æ•°ã®é¸æŠžè‚¢ã‚’æ示ã—ã€ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆå´ã¯ãã®ä¸ã§å„ªå…ˆã™ã‚‹ã‚‚ã®ã‚’1ã¤é¸ã¶ サーãƒãƒ¼ãŒå„ªå…ˆã™ã‚‹ã¹ãé¸æŠžã‚’æŒã£ã¦ã„ãŸã‚‰ã€ã‚µãƒ¼ãƒãƒ¼ã¯ãã®é¸æŠžè‚¢ã® URI å‚照をLocaionヘッダーã«å«ã‚ã‚‹ã¹ã(
モダンWebã«ãŠã‘ã‚‹ã‚ャッシングã®ãŸã‚ã®æ–°HTTP標準 | POSTD
一般ユーザーå‘ã‘ã®å¤§è¦æ¨¡ãªWebサイトやã€ãƒ¢ãƒ€ãƒ³Web上ã§å‹•ä½œã™ã‚‹Webアプリケーションをé‹å–¶ã™ã‚‹å ´åˆã€CDNãªã©ã®ã‚ャッシングサービスã«ã‚ˆã£ã¦é™çš„コンテンツをã‚ャッシュã™ã‚‹ã“ã¨ãŒæ¥µã‚ã¦é‡è¦ã§ã™ã€‚ ã—ã‹ã—ã“ã†ã—ãŸã‚µãƒ¼ãƒ“スã¯ã€éžå¸¸ã«è¤‡é›‘ã§åˆ†ã‹ã‚Šã«ãã„ã‚‚ã®ã§ã™ã€‚ 幸ã„ã€IETF（Internet Engineering Task Force）ã®HTTPワーã‚ンググループãŒã“ã®çŠ¶æ³ã‚’改善ã™ã¹ãã€HTTPã®æ–°æ¨™æº–ç–定ã«å–り組んã§ã„ã¾ã™ã€‚ 最近ã€åŒãƒ¯ãƒ¼ã‚ンググループã§ã¯ã€ã‚ャッシングã®ãƒ‡ãƒãƒƒã‚°ã¨ã‚ャッシュè¨å®šã®ç®¡ç†ã‚’容易ã«ã™ã‚‹ã“ã¨ã‚’目的ã¨ã—ãŸã€HTTPヘッダã«é–¢ã™ã‚‹2ã¤ã®æ–°æ¨™æº–案ã®ç™ºè¡¨ã«å‘ã‘ã¦æ´»ç™ºãªå‹•ããŒã‚ã‚Šã¾ã—ãŸã€‚ ã“ã®ã“ã¨ãŒä½•ã‚’æ„味ã—ã€ã©ã®ã‚ˆã†ã«æ©Ÿèƒ½ã™ã‚‹ã®ã‹ã€ãã—ã¦Web制作ã«æºã‚る開発者全ã¦ãŒãªãœæ³¨ç›®ã™ã¹ããªã®ã‹ã«ã¤ã„ã¦è¦‹ã¦ã„ãã¾ã™ã€‚ 新標準 ã“ã®è¨˜äº‹ã§å–り上ã’る標準案ã¯ä»¥ä¸‹ã®2ã¤ã§ã™ã€‚ Ca
無料プãƒã‚シツール「mitmproxyã€ã‚’使ã£ã¦ã¿ã‚ˆã† - セットアップ方法ã¨ã‚»ã‚ュリティエンジニアãŠã™ã™ã‚ã®è¨å®š - Flatt Security Blog
※本記事ã¯ç†è€…styprãŒè‹±èªžã§åŸ·ç†ã—ãŸè¨˜äº‹ã‚’æ ªå¼ä¼šç¤¾Flatt Security社内ã§æ—¥æœ¬èªžã«ç¿»è¨³ã—ãŸã‚‚ã®ã«ãªã‚Šã¾ã™ã€‚ ã¯ã˜ã‚ã« ã“ã‚“ã«ã¡ã¯ã€Flatt Securityã®stypr(@stereotype32)ã§ã™ã€‚今回ã¯ã‚»ã‚ュリティ診æ–ãªã©ã§ä½¿ã‚れるãƒãƒ¼ã‚«ãƒ«ãƒ—ãƒã‚シツールã«ã¤ã„ã¦ç´¹ä»‹ã—ã¾ã™ã€‚ ã¡ãªã¿ã«ã€é–‹ç™ºè€…ã®çš†ã•ã‚“ãŒè„†å¼±æ€§ã®æ¤œè¨¼ã‚’è¡Œã†ã«ã¯ã“れらã®ãƒ„ールã ã‘ã§ãªãã‚»ã‚ュリティ知è˜ãŒå¿…è¦ã§ã™ãŒã€ãã®ãŸã‚ã«ã¯Flatt SecurityãŒæä¾›ã™ã‚‹ã€ŒKENROã€ãŒãŠã™ã™ã‚ã§ã™ã€‚Web アプリケーションã®ä»£è¡¨çš„ãªè„†å¼±æ€§10個ã«é–¢ã—ã¦ã€è„†å¼±ãªã‚½ãƒ¼ã‚¹ã‚³ãƒ¼ãƒ‰ã‚’ä¿®æ£ã™ã‚‹ãªã©ã®ãƒãƒ³ã‚ºã‚ªãƒ³ã‚’通ã—ã¦å¦ã¶ã“ã¨ãŒã§ãã¾ã™ã€‚ ãœã²ãƒãƒŠãƒ¼ã‚ˆã‚Šç„¡æ–™ãƒ»ç„¡æœŸé™ã®ãƒˆãƒ©ã‚¤ã‚¢ãƒ«ã‚’ã”利用ãã ã•ã„。 ã•ã¦ã€ã‚»ã‚ュリティエンジニアã®å¤šãã¯ã€Webやモãƒã‚¤ãƒ«ã‚¢ãƒ—リケーションã®HTTP/HTTPSトラフィックを確èªã™ã‚‹ã™ã‚‹ãŸã‚ã«Bur
ファイルダウンãƒãƒ¼ãƒ‰å®Œå…¨ãƒžã‚¹ã‚¿ãƒ¼ | フューãƒãƒ£ãƒ¼æŠ€è¡“ブãƒã‚°
Real World HTTPã§ã‚‚紹介ã—ãŸãƒã‚¿ã§ã™ãŒã€ãŠä»•äº‹ã§å—ã‘ã¦ã„る技術コンサルä¸ã«è³ªå•ã‚’ã„ãŸã ã„ãŸæ™‚ã«ã€å¾®å¦™ã«æœ¬ã§ç´¹ä»‹ã—ãŸå†…容ã§ã¯å°‘ã—足りãªã‹ã£ãŸã®ã§ã€æ”¹ã‚ã¦æ•´ç†ã®ãŸã‚ã«ãƒ–ãƒã‚°è¨˜äº‹ã«ã—ã¦ã¿ã¾ã—ãŸã€‚次回ã€æœ¬ãŒæ”¹è¨‚ã•ã‚Œã‚‹ã“ã¨ãŒã‚ã‚Œã°ã“ã®ãƒ–ãƒã‚°ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã®å†…容も入れã¦åŠ ç†ã—ãŸã„ã¨æ€ã„ã¾ã™ã€‚ Real World HTTPã ã¨Goを使ã£ã¦ã„ã¾ã—ãŸãŒã€ãƒ•ãƒãƒ³ãƒˆã¨ã‚µãƒ¼ãƒãƒ¼ã‚’åŒæ™‚ã«ã„ã˜ã‚‹ã®ã§ã€æœ¬ã‚¨ãƒ³ãƒˆãƒªãƒ¼ã§ã¯Next.jsをサンプルã«ä½¿ã„ã¾ã™ã€‚Next.jsã§ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã‚’作ã£ã¦ï¼ˆnpx create-next-app@latest –ts)ã€é©å½“ãªãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆåを入れã¦ã‚¢ãƒ—リケーションã®é››å½¢ã‚’作ã£ã¦ãŠã„ã¦ãã ã•ã„。 Next.jsã§ã¯ã€1ã¤ã®ã‚¹ã‚¯ãƒªãƒ—トファイルを作æˆã™ã‚‹ã¨ã€ãã‚ŒãŒã‚µãƒ¼ãƒãƒ¼API(/pages/api以下)ã¨ã€ãƒ•ãƒãƒ³ãƒˆã®ç”»é¢(/pages/以下ã®api以外)ã«ãªã‚Šã¾ã™ã€‚Next.j
HTTP 関連 RFC ãŒå¤§é‡ã«å‡ºãŸè©±ã¨ 3 è¡Œã¾ã¨ã‚ | blog.jxck.io
Intro 2022/06/06 ~ 9 ã‚ãŸã‚Šã«ã€é•·ãã«æ¸¡ã£ã¦ç–定作æ¥ãŒè¡Œã‚ã‚Œã¦ã„㟠HTTP 関連㮠RFC ãŒå¤§é‡ã«å…¬é–‹ã•ã‚ŒãŸã€‚ RFC 9110: HTTP Semantics RFC 9111: HTTP Caching RFC 9112: HTTP/1.1 RFC 9113: HTTP/2 RFC 9114: HTTP/3 RFC 9163: Expect-CT Extension for HTTP RFC 9204: QPACK: Field Compression for HTTP/3 RFC 9205: Building Protocols with HTTP RFC 9209: The Proxy-Status HTTP Response Header Field RFC 9211: The Cache-Status HTTP Response Header Field
HTTP caching - HTTP | MDN
HTTP Guides An overview of HTTP A typical HTTP session HTTP Messages MIME types (IANA media types) Compression in HTTP HTTP caching HTTP authentication Using HTTP cookies Redirections in HTTP HTTP conditional requests HTTP range requests Content negotiation Connection management in HTTP/1.x Evolution of HTTP Protocol upgrade mechanism Proxy servers and tunneling HTTP Client hints Security and priv
Cache-Control - HTTP | MDN
HTTP Guides Resources and URIs Identifying resources on the Web Data URLs Introduction to MIME types Common MIME types Choosing between www and non-www URLs HTTP guide Basics of HTTP Overview of HTTP Evolution of HTTP HTTP Messages A typical HTTP session Connection management in HTTP/1.x Protocol upgrade mechanism HTTP security Content Security Policy (CSP) HTTP Strict Transport Security (HSTS) X-
Webhook.site - Test, transform and automate Web requests and emails
= appConfig.MaxRequests"> Upgrade to a Webhook.site account to unlock unlimited requests This URL received the maximum of {{ appConfig.MaxRequests }} requests and can't accept more requests, emails or DNSHooks. New requests sent to this URL will return HTTP status code 410 Gone or 429 Too Many Requests and won't be logged. Also note that it is against our terms of service to use Webhook.site for a
オリジン間リソース共有 (CORS) - 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
æ–°ã—ã„HTTPメソッドã€QUERYメソッドã®ä»•æ§˜ - ASnoKaze blog
æ–°ã—ã„HTTPメソッドを定義ã™ã‚‹ã€ŒThe HTTP QUERY Methodã€ã¨ã„ã†æ案仕様ãŒè°è«–ã•ã‚Œã¦ã„ã¾ã™ã€‚ ã‚‚ã¨ã‚‚ã¨ã¯ã€SEARCHメソッドã¨ã„ã†å‘¼ã³åãŒå€™è£œã¨ã—ã¦ã‚ã’られã¦ã„ã¾ã—ãŸãŒã€é•·ã„è°è«–ã®ã®ã¡ã€ä¸€æ—¦QUERYã¨å‘¼ã¶æ–¹å‘ã¨ãªã£ã¦ãŠã‚Šã¾ã™ã€‚最終的ãªFixã«ã¤ã„ã¦ã¯ã€ã“ã® draft 02ã®å…¬é–‹ã¨ã¨ã‚‚ã«æ”¹ã‚ã¦ã‚³ãƒ³ã‚»ãƒ³ã‚µã‚¹ã‚’求ã‚ãŸå¾Œã«è¡Œã‚ã‚Œã¾ã™ã€‚ QUERYメソッド 「GETリクエストã«ãƒœãƒ‡ã‚£ã‚’付ã‘ãŸã„ã¨ã„ã†ã€ã¨ã„ã†è³ªå•ã¯é•·ã‚‰ã有りã¾ã—ãŸã€‚ã—ã‹ã—ã€GETã‚„HEADリクエストã§ãƒœãƒ‡ã‚£ã‚’ã¤ã‘ã‚‹ã“ã¨ã¯éžæŽ¨å¥¨ã¨ãªã£ã¦ã„ã¾ã™ (å‚考URL)。 ãã®ã‚ˆã†ãªè¦æœ›ã®ãªã‹ã§ã€ãƒªã‚¯ã‚¨ã‚¹ãƒˆã§ãƒœãƒ‡ã‚£ã‚’å«ã‚られる冪ç‰æ€§ã®ä¿è¨¼ã•ã‚ŒãŸæ–°ã—ã„HTTPメソッドãŒæ¤œè¨Žã•ã‚Œã¾ã—ãŸã€‚ãã‚ŒãŒQUERYメソッドã§ã™ã€‚冪ç‰æ€§ãŒã‚ã‚‹ãŸã‚ã€ãƒ–ラウザやProxyã¯è‡ªå‹•ã§ãƒªãƒˆãƒ©ã‚¤ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚(ãªãŠã€POSTã¯ã‚»ãƒžãƒ³ãƒ†ã‚£ã‚¯ã‚¹ä¸Šå†ªç‰
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Home - Requestly
HTTPie for Web — API testing client
GitHub - twigly/rust-http-cli: rh is a user-friendly command-line tool to request HTTP APis
{{#tags}}- {{label}}
{{/tags}}