Repository navigation
c0mpute edge: a name pointed at a c0mpute app serves the app - #37
Merged
Merged
Conversation
demo.killer points at a4188f880e3f3b5383b5, which is a c0mpute app (hits-demo, /a/<id>/), not a static site, so the edge asked /s/<id>/ and every gateway said 'no such site on the network (yet)'. The edge now asks our own gateways /apps/v1/apps/<id> (cached 5 min app / 1 min site) and, for an app, proxies every method with its body to /a/<id>/<path> on trusted gateways only, with x-forwarded-host/proto. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
demo.killer.pit.world 404'd "no such site on the network (yet)": the name's c0mpute id a4188f880e3f3b5383b5 is an app (hits-demo, served at /a//), and the edge only knew static sites (/s//).
Now the edge asks its trusted gateways
/apps/v1/apps/<id>(only an answer naming that app_id counts; cached 5 min for an app, 1 min for a site) and serves an app by proxying every method, body included (32 MiB cap), to/a/<id>/<path>with x-forwarded-host/proto. Apps go through our own gateways only: their answers are live and cannot be verified like signed site files. Static sites are unchanged (GET/HEAD, verified reads).Test added; 135/135 pass.
🤖 Generated with Claude Code