<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>HTTP-QUERY-메서드 on gnosyslambda&#39;s log</title>
    <link>https://gnosyslambda.github.io/tags/http-query-%EB%A9%94%EC%84%9C%EB%93%9C/</link>
    <description>Recent content in HTTP-QUERY-메서드 on gnosyslambda&#39;s log</description>
    <image>
      <title>gnosyslambda&#39;s log</title>
      <url>https://gnosyslambda.github.io/images/og-image.png</url>
      <link>https://gnosyslambda.github.io/images/og-image.png</link>
    </image>
    <generator>Hugo</generator>
    <language>ko-KR</language>
    <lastBuildDate>Sun, 05 Jul 2026 07:03:03 +0900</lastBuildDate>
    <atom:link href="https://gnosyslambda.github.io/tags/http-query-%EB%A9%94%EC%84%9C%EB%93%9C/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP QUERY 메서드와 API 조회 설계</title>
      <link>https://gnosyslambda.github.io/posts/2026-07-05-http-query-api-design/</link>
      <pubDate>Sun, 05 Jul 2026 07:03:03 +0900</pubDate>
      <guid>https://gnosyslambda.github.io/posts/2026-07-05-http-query-api-design/</guid>
      <description>RFC 10008 HTTP QUERY 메서드가 GET·POST의 한계를 어떻게 바꾸는지, 캐싱·재시도·CDN·호환성 리스크까지 실무 관점에서 정리합니다.</description>
    </item>
  </channel>
</rss>
