gateways

Configure IPFS HTTP gateways with origin isolation, CORS, and rate-limiting.

1|Updated Apr 15, 2026

Search Tags:#security #cors #gateway #subdomain #trustless #ipfs #origin-isolation

Ready to run

npx skills add https://github.com/MysticRyuujin/spirens --skill gateways

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gateways
Source: https://github.com/MysticRyuujin/spirens/tree/main/gateways
Command: npx skills add https://github.com/MysticRyuujin/spirens --skill gateways

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

IPFS gateways can expose content with varying isolation, security, and performance characteristics. This Skill guides you through choosing between path-based and subdomain gateways, trusted vs trustless responses, CORS handling, and rate-limiting strategies to avoid public gateway abuse.

Core Features & Use Cases

Path vs subdomain gateway differences and their implications for origin isolation and link validity.
Security and verification: trusted vs trustless gateways and how clients can verify content.
Operational considerations: CORS, rate-limiting, TLS termination, and public vs private gateway deployment.

Quick Start

Configure a per-CID subdomain gateway and test access to a sample IPFS content to validate origin isolation and CORS settings.

Frequently Asked Questions about gateways

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I configure an IPFS gateway for secure content exposure?▼

Configure an IPFS gateway for secure content exposure by choosing between path-based or per-CID subdomain deployments, setting up TLS termination with wildcard certificates, and applying CORS rules. This ensures proper origin isolation and safe HTTP access.

What is the difference between path-based and subdomain IPFS gateways?▼

Path-based IPFS gateways serve content from a single origin, limiting browser origin isolation, while subdomain gateways assign each CID a unique subdomain. Subdomain gateways provide stronger origin isolation and maintain link validity for web applications.

How do trusted and trustless IPFS gateway responses differ?▼

Trusted IPFS gateway responses rely on the gateway to verify content authenticity, whereas trustless responses allow clients to independently verify content using cryptographic proofs. Trustless gateways ensure end users can validate the data without gateway trust.

How do I set up CORS and rate-limiting for a public IPFS gateway?▼

Set up CORS and rate-limiting for a public IPFS gateway by configuring HTTP response headers for cross-origin access and applying request rate limits. These strategies prevent public gateway abuse while allowing controlled external access.

Do I need wildcard certificates for TLS termination on subdomain gateways?▼

Yes, wildcard certificates are required for TLS termination on subdomain gateways. Because per-CID subdomain gateways dynamically generate hostnames for each content identifier, a wildcard certificate secures all dynamically created subdomains.

When should I not use a public IPFS gateway?▼

Avoid using a public IPFS gateway when serving private or restricted content without strict access controls, or when origin isolation is critical but only a path-based gateway is available. Public gateways lack rate-limiting and access restrictions by default.