Serve different response types from the same URL based on the Accept header.
npx skills add https://github.com/rangojs/rango --skill mime-routes-rangojs
Please help me install this Agent Skill. Skill: mime-routes Source: https://github.com/rangojs/rango/tree/main/packages/rangojs-router/skills/mime-routes Command: npx skills add https://github.com/rangojs/rango --skill mime-routes-rangojs
High-intent search queries and answers about installing and using this skill.
Register an RSC route with path() and a JSON variant with path.json() on the same URL pattern in your urls() array. The router inspects the Accept header and dispatches to the matching handler, adding Vary: Accept automatically.
Rango parses q-values first, then uses client ordering as a tiebreaker, then specific MIME matches. Wildcards and missing Accept headers fall back to route definition order, with the first-defined variant winning.
Yes, two or more response-type routes like path.json and path.text can share a URL without an RSC route. The last registered route becomes the primary and the Accept header picks among the response-type candidates directly.
Yes, all negotiated responses automatically include the Vary: Accept header. This tells CDNs and HTTP caches to store separate entries per Accept header value, so no additional cache configuration is needed.
The flight format is explicit opt-in only, served when the client sends Accept: text/x-component or the internal transport params the Rango client runtime sends. Browsers, curl, and generic HTTP clients always receive the HTML document.
wheels-devGenerate RESTful, nested, and custom routes for CFWheels applications.
chatbotkitIdentify and reproduce cache-poisoning vulnerabilities in CDN-backed applications.
supersterlingEnable Partial Prerendering with cacheComponents and use cache in Next.js 16.
DanielPodolskyEvaluate API route handlers and backend architecture for RESTful design.
