syntaqxA host a cloud job's guardrails refuse is named in the refusal's status line, not only its body: `403 Forbidden by g1t guardrails: api.expo.dev is not an allowed domain`. Many tools show only the status line of a failed request. eas-cli's GraphQL client prints the reason phrase and drops a body that is not JSON, and apk prints `HTTP 403: Forbidden`, so a refused Expo call surfaced as a bare "Forbidden" followed by "GraphQL request failed", with nothing pointing at the guardrails. The refusal also carries an x-g1t-blocked-host header beside x-g1t-guardrails: blocked. Its plain-text body says where to allow the host: Allowed domains for every sandbox, or Workflow-only domains for the jobs of one workflow and environment. The guardrails and Actions guides say what a refused request shows.3039e06History
- ..
- accordion.tsx
- alert-dialog.tsx
- alert.tsx
- avatar.tsx
- badge.tsx
- breadcrumb.tsx
- button.tsx
- card.tsx
- checkbox.tsx
- collapsible.tsx
- combobox.tsx
- command.tsx
- dialog.tsx
- dropdown-menu.tsx
- field.tsx
- file-drop.tsx
- hint.tsx
- hover-card.tsx
- index.tsx
- input.tsx
- kbd.tsx
- label.tsx
- popover.tsx
- progress.tsx
- radio-group.tsx
- scroll-area.tsx
- select.tsx
- separator.tsx
- sheet.tsx
- sidebar.tsx
- skeleton.tsx
- slider.tsx
- switch.tsx
- tab-strip.tsx
- table.tsx
- tabs.tsx
- textarea.tsx
- toggle-group.tsx
- tooltip.tsx