Repository navigation
Serve executor.sh's forwarded paths from an unplaced front Worker - #2225
Merged
Merged
Conversation
RhysSullivan
added this pull request to stack #2227
October 8, 2026 22:19
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| 🔵 In progress View logs |
executor-marketing | 28edc51 | Oct 08 2026, 10:37 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| 🔵 In progress View logs |
executor-cloud | 28edc51 | Oct 08 2026, 10:37 PM |
Contributor
Cloudflare previewTorn down — the PR is closed. |
@executor-js/cli
@executor-js/config
@executor-js/execution
@executor-js/sdk
@executor-js/codemode-core
@executor-js/runtime-quickjs
@executor-js/plugin-file-secrets
@executor-js/plugin-graphql
@executor-js/plugin-keychain
@executor-js/plugin-mcp
@executor-js/plugin-onepassword
@executor-js/plugin-openapi
executor
commit: |
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
1 participant
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.
executor-cloud is placed in Virginia, so every request its edge forwards to v2 or to v1's marketing worker crossed there first (cf-placement: remote-IAD on /_astro files, 1.2–2.7 s spikes). A new Worker, executor-cloud-edge, with no placement, runs the same edge on a zone route
executor.sh/*, which runs before the Custom Domain. It passes v1's own requests on to executor-cloud withfetch(request), unchanged.Rollback:
wrangler delete --name executor-cloud-edgeremoves the Worker and its route. executor-cloud keeps its own copy of the edge, so the domain behaves as it does today.