Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| return new Response(JSON.stringify(json), { | ||
| status: 200, | ||
| headers: { | ||
| 'Content-Type': 'application/json', |
There was a problem hiding this comment.
Preserve upstream status and headers when proxying authorize response
The handler always rewraps a successful upstream response into new Response(JSON.stringify(json), { status: 200, headers: { 'Content-Type': 'application/json' } }). This discards the status code and all headers returned by the Layercode endpoint, notably Set-Cookie and any non‑200 status codes. If the authorize endpoint relies on cookies or returns 401/403 for invalid credentials, the caller will never see those headers or the correct status, so the session flow cannot succeed. Consider returning the original response (or cloning it) so status and headers propagate intact.
Useful? React with 👍 / 👎.
No description provided.