---
title: "RFC 10008: HTTP Query for Headless Frontends Explained"
canonical_url: "https://www.laioutr.com/en/blog/rfc-10008-http-query-headless-frontend"
locale: en
meta:
  description: "See how RFC 10008 defines HTTP query handling for headless frontends: syntax, caching impact, and implementation notes for your storefront stack."
  "og:description": "See how RFC 10008 defines HTTP query handling for headless frontends: syntax, caching impact, and implementation notes for your storefront stack."
  "og:title": "RFC 10008: HTTP Query for Headless Frontends Explained"
---

![Hero en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqusawpa3pgo06l96mfqybll)

# RFC 10008: The New HTTP Method That Makes You Rethink Headless Storefronts

Table of contents

1. [1.The problem QUERY solves](#the-problem-query-solves)
2. [2.What QUERY does differently](#what-query-does-differently)
3. [3.Being honest about the adoption path](#being-honest-about-the-adoption-path)
4. [4.Why this is a strategic question - not just a technical one](#why-this-is-a-strategic-question-not-just-a-technical-one)
5. [5.What this means for you - today](#what-this-means-for-you-today)
6. [6.Build on a frontend-independent foundation](#build-on-a-frontend-independent-foundation)
7. [7.Frequently asked questions about RFC 10008](#frequently-asked-questions-about-rfc-10008)

1. [1.The problem QUERY solves](#the-problem-query-solves)
2. [2.What QUERY does differently](#what-query-does-differently)
3. [3.Being honest about the adoption path](#being-honest-about-the-adoption-path)
4. [4.Why this is a strategic question - not just a technical one](#why-this-is-a-strategic-question-not-just-a-technical-one)
5. [5.What this means for you - today](#what-this-means-for-you-today)
6. [6.Build on a frontend-independent foundation](#build-on-a-frontend-independent-foundation)
7. [7.Frequently asked questions about RFC 10008](#frequently-asked-questions-about-rfc-10008)

In June 2026, the IETF published a new HTTP standard that almost nobody in commerce frontend circles is talking about. RFC 10008 defines a new HTTP method: **QUERY**. That sounds unspectacular. I think it is not.

## The problem QUERY solves

Every headless frontend lives on queries. Search, faceted filtering, product listings, GraphQL queries, personalisation - all of these are, at their core, structured requests to a data endpoint. Until now, we had exactly two options for that, and both are unsatisfying.

**GET** is semantically the right choice: cacheable, safe (does not trigger a state change), idempotent (safe to repeat automatically). But the query must live in the URL. RFC 9110 recommends staying under 8,000 octets in URL length - with complex filter structures, nested GraphQL queries, or personalised search requests, that ceiling arrives quickly. Beyond that, query parameters end up in logs, proxy records, and browser history. Not ideal for parameters that carry any degree of sensitivity.

**POST** solves the URL problem: the payload goes in the body, arbitrarily large, no URL limit. But POST is semantically neither safe nor idempotent - the HTTP layer cannot know whether a repeated POST is harmless or triggers a state change. The consequence: CDNs and edge proxies do not cache POST. This is exactly why almost every GraphQL query today bypasses the CDN and hits the origin directly. Persisted queries, query hashing, CDN workarounds - these are all patches for this fundamental mismatch. I've written about why workarounds like these compound into real cost over time in our [composable reality check](https://www.laioutr.com/en/blog/composable-rush-not-paying-off).

## What QUERY does differently

RFC 10008 closes this gap with a new HTTP method that combines both properties. The formal definition (Abstract, §2, Table 1 of the RFC):

- **Payload in the body** - like POST, no URL limit, no URL leakage
- **Explicitly safe** - QUERY has no side effect; the server may treat that as a guarantee
- **Explicitly idempotent** - an HTTP client, proxy, or CDN may repeat QUERY requests without risk

This is not a semantic subtlety. It is the foundation on which CDNs and edge caches make caching decisions. With QUERY, complex search requests and filter queries can once again be cached at the edge - the cache key includes the request body and request metadata (§2.7). Origin load decreases, latency decreases, storefronts become faster without any change to the business logic layer.

RFC 10008 also introduces the `Accept-Query` header field (§3). It makes it machine-discoverable which query formats an endpoint supports - a clean basis for format discovery instead of hardcoded client assumptions.

One important note on the CORS side: because QUERY is not on the CORS safelist of methods in the WHATWG Fetch standard, it triggers a preflight request (§4 Security Considerations). That is not a bug; it is the expected consequence of a new method. This needs to be accounted for on the browser side.

## Being honest about the adoption path

GraphQL-over-QUERY is not part of RFC 10008 and has not been standardised. RFC 10008 defines the method, not the payload formats. Whether and how GraphQL clients adopt QUERY will be a separate discussion. I mention it here because it could, in the medium term, make persisted query workarounds unnecessary - as a possibility, not a promise.

And even when clients are ready: servers, CDNs, reverse proxies, and browsers all need to support QUERY before the standard is usable in production in a meaningful way. This is a multi-year road. Writing about it now is not because QUERY is production-ready tomorrow. It is because the right time to think about a standard is not when it has already shipped everywhere.

## Why this is a strategic question - not just a technical one

Here it gets interesting, and here is the point where the architecture decision we made at Laioutr becomes relevant to me.

If you have built a headless frontend as **custom software** - your own Next.js project, a Nuxt application, your own API layer - you will need to implement QUERY support in every storefront individually. Touch the transport layer. Rethink caching logic. Handle CORS and preflight. Define retry strategies. Configure cache keys. Test everything. Per project. Again and again, for each client, for each storefront.

This is not a technical problem solved once. It is a multiplication problem: as many projects as storefronts.

If you build on a **platform**, your starting position is different. At Laioutr, we abstract the data and transport layer. Our customers compose sections and blocks - they do not wire HTTP calls by hand. The platform owns the layer where QUERY becomes relevant.

What that means in practice: once the ecosystem is ready - servers, CDNs, browsers, GraphQL clients - we can adopt the standard **centrally**. Every storefront on Laioutr benefits without a single customer touching their code. No 50 parallel migration tickets. No divergence between older and newer projects. It is the same logic that lets us make [switching commerce vendors without a full replatforming](https://www.laioutr.com/en/blog/switching-vendors-without-replatforming) possible - the platform absorbs the change, not the customer.

We are preparing the platform for this today. Not because QUERY is going live tomorrow, but because architecture decisions that need to be elastic later have to be made early.

## What this means for you - today

If you are building headless on custom software, RFC 10008 is not an operational priority today. But it is a good moment to ask two questions.

**First question:** Who in your architecture owns the transport layer? If the answer is "we do - per project", that is a signal about the kind of effort protocol shifts like this one will create. Frontend independence is becoming a buying criterion for exactly these reasons - [more on that in our weekly wrap](https://www.laioutr.com/en/blog/frontend-independence-buying-criterion-2026-wrap).

**Second question:** Which of your current workarounds - persisted queries, query hashing, CDN bypasses - are actually solving a problem that a cleaner HTTP foundation would remove on its own?

A frontend management platform is not there to take those questions away from you. It is there so that you do not have to encode your answers to them in transport layer code.

RFC 10008 is published: https://www.rfc-editor.org/rfc/rfc10008.html. Authors: J. Reschke (greenbytes), J. M. Snell (Cloudflare), M. Bishop (Akamai). Standards Track, June 2026.

If you are building headless and want to understand what QUERY means concretely for your architecture - write to me or [book a demo](https://www.laioutr.com/en/).

## Build on a frontend-independent foundation

[Composable Headless Frontend](https://www.laioutr.com/en/composable-headless-frontend) · [Performance & Core Web Vitals](https://www.laioutr.com/en/product/performance-core-web-vitals) · [Agentic Frontend Management Platform](https://www.laioutr.com/en/agentic-frontend-management-platform)

## Frequently asked questions about RFC 10008

### What is RFC 10008?

RFC 10008 standardises the HTTP QUERY method: a request method that is safe and idempotent like GET, but can carry a request body like POST. It closes the long-standing gap between GET (no body, limited URL length) and POST (a body, but not safe, idempotent, or cacheable).

### What does the HTTP QUERY method change for headless frontends?

It lets a storefront send complex search, filter, and GraphQL-style requests in a request body while the response stays cacheable and idempotent. For product listing pages, faceted search, and search-as-a-service calls, that means CDN-level caching that POST could never deliver, without cramming state into ever-longer URLs.

### Is HTTP QUERY the same as sending GraphQL over GET?

No. GraphQL over GET works only for small queries because the whole query has to fit in the URL, and it is easy to exceed URL length limits. HTTP QUERY carries the query in the body with no practical size limit, and it is defined as safe and idempotent, so intermediaries and CDNs may cache the response.

### When can we use RFC 10008 in production?

Adoption depends on client, server, and CDN support rolling out across the stack. The pragmatic path today is feature detection with a POST fallback: use HTTP QUERY where the whole chain supports it, and fall back to POST elsewhere, so nothing breaks while support matures.

---

Share this article

[Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Frfc-10008-http-query-headless-frontend) [Share on X](https://x.com/intent/post?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Frfc-10008-http-query-headless-frontend&text=) [Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Frfc-10008-http-query-headless-frontend) [Share on Pinterest](https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Frfc-10008-http-query-headless-frontend&description=) [Share via email](mailto:?subject=&body=%0A%0Ahttps%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Frfc-10008-http-query-headless-frontend)

## More articles on frontend and headless

Practical know-how for frontend development, smart agents, and headless

[To the blog](https://www.laioutr.com/en/blogs/insights)

[![Hero product configurator types ecommerce frontend guide 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwma9ijf0avu07mjf0kppi1h)<h3>Product Configurators: 5 Types and What They Ask of the Frontend</h3>Product configurators in e-commerce fall into five types: variant selection, rule-based configurator…](https://www.laioutr.com/en/blog/product-configurator-types-ecommerce-frontend-guide-2026)

[![Hero landing page builder vs frontend management platform en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwma6j6w073k06me93xaps4m)<h3>Landing Page Builder or Frontend Management Platform?</h3>A landing page builder is the right tool for short-lived campaign pages outside the shop: lead forms…](https://www.laioutr.com/en/blog/landing-page-builder-vs-frontend-management-platform)

[![Hero self service kiosk ticketing frontend conversion 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwma4cbg03pt07mjum2wr1u8)<h3>Ticket Kiosks That Convert: Frontend Patterns for Attractions</h3>A self-service ticket kiosk converts when guests understand it without help and complete the purchas…](https://www.laioutr.com/en/blog/self-service-kiosk-ticketing-frontend-conversion-2026)

[![Hero magento frontend build model decision matrix en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwma36tc020i06me6brdswcl)<h3>Magento Frontend: In-House, Composable, FEaaS or Custom PWA?</h3>There are four build models for a Magento frontend: an in-house build by an internal team, a composa…](https://www.laioutr.com/en/blog/magento-frontend-build-model-decision-matrix)

[![Hero mobile search ux best practices in app search storefront en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwma332u01m906me5dhqy81s)<h3>Mobile Search UX: Best Practices for In-App and Storefront Search</h3>Good mobile search starts with a visible search field instead of a hidden icon, opens a dedicated se…](https://www.laioutr.com/en/blog/mobile-search-ux-best-practices-in-app-search-storefront)

[![Hero video cdn ecommerce product videos without buffering en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwma2dsv00eu06megpcgsz9z)<h3>Video CDN for E-Commerce: Product Videos Without Buffering</h3>A video CDN for e-commerce delivers product videos from servers close to shoppers and continuously a…](https://www.laioutr.com/en/blog/video-cdn-ecommerce-product-videos-without-buffering)

[![Hero law firm website clients professional rules visibility en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwma05bdl7lx06mc9v716g03)<h3>Law Firm Websites in Germany: Clients, Rules and Visibility</h3>A law firm website wins clients when it answers concrete questions for each practice area, presents …](https://www.laioutr.com/en/blog/law-firm-website-clients-professional-rules-visibility)

[![Hero composable commerce platform buyer guide midmarket b2b enterprise en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwm9zs0tlauc06la4yfsa59j)<h3>Choosing Composable Commerce: Mid-Market, B2B and Enterprise</h3>The right composable commerce platform depends less on the feature list than on the starting point: …](https://www.laioutr.com/en/blog/composable-commerce-platform-buyer-guide-midmarket-b2b-enterprise)

[![Hero attractions ecommerce ticket shop own site frontend 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwm9yolykr1g07mk0vur6t3y)<h3>Sell Tickets on the Attraction's Own Site: The Ticket Frontend</h3>Theme parks, museums, zoos and other attractions sell more tickets on their own website when three t…](https://www.laioutr.com/en/blog/attractions-ecommerce-ticket-shop-own-site-frontend-2026)

[![Hero frontend data layer orchestr multiple backends en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwm9x06nl37g06mc8mugijwp)<h3>A Frontend Data Layer Across Many Backends: How Orchestr Works</h3>A frontend data layer is the layer between storefront and backends that turns data from the commerce…](https://www.laioutr.com/en/blog/frontend-data-layer-orchestr-multiple-backends)

[![Hero hreflang locale routing market fallbacks seo geo en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwm9vfnnl5b106lahk73ydjs)<h3>hreflang, Locale Routing, Fallbacks: SEO for Multi-Market Stores</h3>Whether search engines and AI systems find the right language and market version of a multi-market s…](https://www.laioutr.com/en/blog/hreflang-locale-routing-market-fallbacks-seo-geo)

[![Hero frontend projects with agencies collaboration model en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwm9uk46kn0o07mkzy6xvjss)<h3>Frontend Projects with Agencies: Roles, Contracts and Rhythm</h3>A frontend project with an agency works when three things are settled before the first sprint: who d…](https://www.laioutr.com/en/blog/frontend-projects-with-agencies-collaboration-model)

[![Hero figma to storefront commerce page without handoff loss en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwm9u093km0a07mkeju33dqv)<h3>Figma to Storefront: Commerce Pages Without Handoff Loss</h3>The path from Figma to a live commerce page rarely breaks on visuals; it almost always breaks on dat…](https://www.laioutr.com/en/blog/figma-to-storefront-commerce-page-without-handoff-loss)

[![Hero digital product passport online shop frontend en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwm9s6ekkxp106mcttfpy909)<h3>Digital Product Passport in Online Stores: The Frontend View</h3>The Digital Product Passport (DPP) is a product-level data record that the EU Ecodesign for Sustaina…](https://www.laioutr.com/en/blog/digital-product-passport-online-shop-frontend)

[![Hero ai product search hybrid search conversion metrics en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmwm9s181kxg006mc0wy9jdi5)<h3>AI Product Search That Converts: Hybrid Search and Metrics</h3>AI-powered product search converts better when it understands the queries where classic keyword sear…](https://www.laioutr.com/en/blog/ai-product-search-hybrid-search-conversion-metrics)

## Apps for the Laioutr platform

[View all apps](https://www.laioutr.com/en/apps)

[![App Shopify](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2kpsk1o07mljlgx3ma7)](https://www.laioutr.com/en/apps/shopify)

Laioutr

[Shopify](https://www.laioutr.com/en/apps/shopify)

Shopify is a commerce platform for selling online and in physical retail.

[![App shopware](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2mzsmns07l8mxvvlllb)](https://www.laioutr.com/en/apps/shopware)

Laioutr

[Shopware](https://www.laioutr.com/en/apps/shopware)

Shopware is a flexible ecommerce platform from Europe for product catalogs and omnichannel commerce.

[![App adobe commerce](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p22msmn707l8yvl65rea)](https://www.laioutr.com/en/apps/adobe-commerce)

Laioutr

[Adobe Commerce](https://www.laioutr.com/en/apps/adobe-commerce)

Adobe Commerce is an enterprise commerce platform for complex, global B2C and B2B scenarios.

Planned

[![App B2B sellers suite](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmno8wnogmesx08l8ogxv3gid)](https://www.laioutr.com/en/apps/b2b-sellers)

Laioutr

[B2Bsellers](https://www.laioutr.com/en/apps/b2b-sellers)

B2B suite for Shopware that turns an online store into a professional B2B commerce platform.

Planned

[![App commerce layer](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p24vsk1a07mlrun4pqiv)](https://www.laioutr.com/en/apps/commerce-layer)

Laioutr

[Commerce Layer](https://www.laioutr.com/en/apps/commerce-layer)

Commerce Layer is a headless commerce platform for making inventory and catalogs available online.

[![App commercetools](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p29pbwz607lb1smrjjd3)](https://www.laioutr.com/en/apps/commercetools)

Laioutr

[Commercetools](https://www.laioutr.com/en/apps/commercetools)

Commercetools is a SaaS-based headless ecommerce platform used worldwide.

[![App emporix](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2c5bwzd07lb4cihw58l)](https://www.laioutr.com/en/apps/emporix)

Laioutr

[Emporix](https://www.laioutr.com/en/apps/emporix)

Emporix is a composable, API-first commerce platform for scalable B2B and B2C scenarios.

Planned

[![App HCL Software](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmlknq0xp7nkt06mm3nhm6vpf)](https://www.laioutr.com/en/apps/hcl-software)

Laioutr

[HCL Software](https://www.laioutr.com/en/apps/hcl-software)

Enterprise suite for digital commerce and experience with extensive configurability.

Planned

[![App intershop](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmlknq10d7zbz06l44qdcwpao)](https://www.laioutr.com/en/apps/intershop)

Laioutr

[Intershop](https://www.laioutr.com/en/apps/intershop)

Enterprise commerce platform for complex B2B and B2C business models.

Planned

[![App magento 2](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmm1svkn1mbb407l6vo1np8s2)](https://www.laioutr.com/en/apps/magento-2)

Laioutr

[Magento 2](https://www.laioutr.com/en/apps/magento-2)

Widely used, extensible commerce platform for B2C and B2B scenarios.

[![App Oxid](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2eask1h07mlr6q5kx0k)](https://www.laioutr.com/en/apps/oxid-eshop)

Laioutr

[OXID eShop](https://www.laioutr.com/en/apps/oxid-eshop)

OXID eShop is an extensible commerce platform for complex B2B and B2C requirements.

Planned

[![App cover patchworks](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmph2jgr7bs5e08la66xwac9q)](https://www.laioutr.com/en/apps/patchworks)

Laioutr

[Patchworks](https://www.laioutr.com/en/apps/patchworks)

Patchworks is a low-code iPaaS that connects ecommerce, ERP, WMS, 3PL, and marketplaces.

Planned

[![App PRESTASHOP](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmpcdbhqnm8st07mn8aol584c)](https://www.laioutr.com/en/apps/PrestaShop)

Laioutr

[Prestashop](https://www.laioutr.com/en/apps/PrestaShop)

Open-source commerce platform for small and midsize merchants in Europe and beyond.

Planned

[![App saleor](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmpcdbhwsmjzr07milpv60c1r)](https://www.laioutr.com/en/apps/saleor)

Laioutr

[Saleor](https://www.laioutr.com/en/apps/saleor)

Open-source, API-first commerce platform built on GraphQL for custom storefronts.

Planned

[![App Commercecloud](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p26ysmne07l82vn6q45s)](https://www.laioutr.com/en/apps/salesforce-commerce-cloud)

Laioutr

[Salesforce Commerce Cloud](https://www.laioutr.com/en/apps/salesforce-commerce-cloud)

Salesforce Commerce Cloud is a cloud-based enterprise commerce platform for businesses of any size.

Planned

[![App SAP](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2gasmnl07l8u6936vg4)](https://www.laioutr.com/en/apps/sap-commerce-cloud)

Laioutr

[SAP Commerce Cloud](https://www.laioutr.com/en/apps/sap-commerce-cloud)

Enterprise commerce platform for complex catalogs, pricing models, and omnichannel journeys.

Planned

[![App SCAYLE](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2ihbwzk07lbl6d3mrzy)](https://www.laioutr.com/en/apps/scayle)

Laioutr

[Scayle](https://www.laioutr.com/en/apps/scayle)

SCAYLE is a commerce engine that helps brands and retailers scale their business.

Planned

[![App spryker](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2p4sk1v07ml2vx76nwh)](https://www.laioutr.com/en/apps/spryker)

Laioutr

[Spryker](https://www.laioutr.com/en/apps/spryker)

Composable commerce platform for sophisticated B2B and B2C business models.

[![App Sylius](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2rhbwzr07lbmrgxt51s)](https://www.laioutr.com/en/apps/sylius)

Laioutr

[Sylius](https://www.laioutr.com/en/apps/sylius)

Sylius is a developer-friendly ecommerce framework for B2C and B2B shopping experiences.

Planned

[![App vendure](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2tgsk2207mltugd287f)](https://www.laioutr.com/en/apps/vendure)

Laioutr

[Vendure](https://www.laioutr.com/en/apps/vendure)

Vendure is a headless commerce platform for businesses with complex requirements.

Coming Soon

[![App VTEX](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmk19p2vosmnz07l8d45obeq9)](https://www.laioutr.com/en/apps/vtex)

Laioutr

[VTEX](https://www.laioutr.com/en/apps/vtex)

Cloud-native, composable commerce platform for B2B and B2C at scale.

Planned

[![App Websale](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:400/auto_image/cmkav7t75rwim06l1v4t9o0cb)](https://www.laioutr.com/en/apps/websale)

Laioutr

[Websale](https://www.laioutr.com/en/apps/websale)

Stable, enterprise-ready commerce backend for complex retail environments.

![Strategy call about the Laioutr platform](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:1024/auto_image/cmolld7ym133w07les4g75kr9)

Strategy call

## The frontend as a control layer

A conversation about stack, roadmap and replatforming scenario. The outcome: a clear picture of how Laioutr fits, what it costs and how fast the go-live can happen.  
  
*"After 30 minutes, we knew Laioutr makes our replatforming feasible."*  
*Daniel B., CEO,* [*hygibox.de*](https://hygibox.de)

[Book a demo](https://www.laioutr.com/en/contact)

## Structured Data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.laioutr.com/#identity",
      "name": "Laioutr",
      "legalName": "Laioutr GmbH",
      "url": "https://www.laioutr.com/",
      "logo": {
        "@type": "ImageObject",
        "url": "https://www.laioutr.com/laioutr-logo.png",
        "width": 400,
        "height": 400
      },
      "email": "info@laioutr.com",
      "telephone": "+49 30 75435715",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "Münchweilersteig 5",
        "postalCode": "12559",
        "addressLocality": "Berlin",
        "addressCountry": "DE"
      },
      "vatID": "DE450905846",
      "sameAs": [
        "https://www.linkedin.com/company/laioutr",
        "https://www.youtube.com/@Laioutr",
        "https://x.com/laioutr"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://www.laioutr.com/en/#website",
      "url": "https://www.laioutr.com/en/",
      "name": "Laioutr",
      "inLanguage": "en",
      "publisher": {
        "@id": "https://www.laioutr.com/#identity"
      }
    },
    {
      "@type": "BlogPosting",
      "@id": "https://www.laioutr.com/en/blog/rfc-10008-http-query-headless-frontend#article",
      "headline": "RFC 10008: The New HTTP Method That Makes You Rethink Headless Storefronts",
      "description": "See how RFC 10008 defines HTTP query handling for headless frontends: syntax, caching impact, and implementation notes for your storefront stack.",
      "image": [
        "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqusawpa3pgo06l96mfqybll"
      ],
      "datePublished": "2026-10-26T11:02:52.68938+00:00",
      "dateModified": "2026-10-26T11:02:52.223161+00:00",
      "inLanguage": "en",
      "articleSection": "Insights",
      "keywords": "Headless Commerce, Composable, Frontend Management, Edge, Industry & Trends",
      "author": {
        "@type": "Person",
        "name": "Marcel Thiesies",
        "jobTitle": "Co-Founder & CEO, Laioutr",
        "image": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmj01b962364n07lb0iguvts5"
      },
      "publisher": {
        "@id": "https://www.laioutr.com/#identity"
      },
      "mainEntityOfPage": {
        "@id": "https://www.laioutr.com/en/blog/rfc-10008-http-query-headless-frontend#webpage"
      },
      "isPartOf": {
        "@id": "https://www.laioutr.com/en/#website"
      }
    },
    {
      "@type": "WebPage",
      "@id": "https://www.laioutr.com/en/blog/rfc-10008-http-query-headless-frontend#webpage",
      "url": "https://www.laioutr.com/en/blog/rfc-10008-http-query-headless-frontend",
      "name": "RFC 10008: The New HTTP Method That Makes You Rethink Headless Storefronts",
      "description": "See how RFC 10008 defines HTTP query handling for headless frontends: syntax, caching impact, and implementation notes for your storefront stack.",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://www.laioutr.com/en/#website"
      },
      "breadcrumb": {
        "@id": "https://www.laioutr.com/en/blog/rfc-10008-http-query-headless-frontend#breadcrumb"
      },
      "primaryImageOfPage": {
        "@type": "ImageObject",
        "url": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmqusawpa3pgo06l96mfqybll"
      },
      "datePublished": "2026-10-26T11:02:52.68938+00:00",
      "dateModified": "2026-10-26T11:02:52.223161+00:00",
      "mainEntity": {
        "@id": "https://www.laioutr.com/en/blog/rfc-10008-http-query-headless-frontend#article"
      }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://www.laioutr.com/en/blog/rfc-10008-http-query-headless-frontend#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Laioutr",
          "item": "https://www.laioutr.com/en/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Insights",
          "item": "https://www.laioutr.com/en/blogs/insights"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "RFC 10008: The New HTTP Method That Makes You Rethink Headless Storefronts"
        }
      ]
    }
  ]
}
```
