Spec CORS config between ThreadCraft (localhost:3000) and easystitch-service (localhost:8080) #13
Labels
No labels
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:verify-failed
bug
deferred
feature-request
in-progress
needs-decompose
needs-triage
quickfix
security/medium
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/Kimi_Agent_Brother_10_Digitizing_App#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
easystitch-service#1 shipped without a CORS middleware. The Vite dev proxy in service#3 only works for
/api/easystitch/*requests routed through the proxy. Direct fetches from the browser to the service URL (preview mode, production behind a different origin) will be blocked.Decide:
http://localhost:3000and the prod frontend origin in the service's CORS middlewareAcceptance: a test in easystitch-service proving an OPTIONS preflight from the frontend origin returns the right headers, AND ThreadCraft can call the service from the browser console without going through the vite proxy.
Auto-triage: needs decompose
Marked
triage-approved+needs-decompose. decompose-executor will pick this up and break it into implementable sub-issues.