Skip to content

IPIP-518: URIs in Routing V1 API via Generic Schema #518

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lidel wants to merge 4 commits into
base: main
Choose a base branch
from
+663 −20
Open

IPIP-518: URIs in Routing V1 API via Generic Schema #518

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c879baf
ipip-518: http(s) urls in routing v1
lidel Oct 13, 2025
e74d686
ipip-518: pivot to generic schema with URI support
lidel Feb 11, 2026
a7ce641
Merge branch 'main' into ipip-0518-https-urls-in-routing-v1
lidel Feb 11, 2026
894f934
chore: upgrade spec-generator to 1.7.0
lidel Feb 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
259 changes: 255 additions & 4 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,6 @@
"license": "",
"private": true,
"dependencies": {
"spec-generator": "^1.6.1"
"spec-generator": "^1.7.0"
}
}
4 changes: 2 additions & 2 deletions src/http-gateways/path-gateway.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ thanks:
name: Protocol Labs
url: https://protocol.ai/
xref:
- url
- rfc3986
- trustless-gateway
- subdomain-gateway
- dnslink-gateway
Expand Down Expand Up @@ -518,7 +518,7 @@ When deserialized responses are enabled,
and no explicit response format is provided with the request, and the
requested data itself has no built-in content type metadata, implementations
SHOULD perform content type sniffing based on file name
(from :ref[url] path, or optional [`filename`](#filename-request-query-parameter) parameter)
(from URI path, or optional [`filename`](#filename-request-query-parameter) parameter)
and magic bytes to improve the utility of produced responses.

For example:
Expand Down
Loading