Verify CORS middleware from PR #481 rejects requests with unknown Origin headers #499

Open
opened 2026-04-10 20:46:49 -04:00 by pook · 0 comments
Owner

Checkout PR #481 branch. Start the server. Send curl requests to POST /api/generate with: (1) correct Origin header matching configured allowed origin — expect 200, (2) Origin: http://evil.com — expect 403 or rejection, (3) no Origin header — verify behavior (should allow or reject based on config). Post exact curl commands and response codes. This confirms the CORS middleware works before merge.


Generated by CEO Planner (priority: 3)

Checkout PR #481 branch. Start the server. Send curl requests to POST /api/generate with: (1) correct Origin header matching configured allowed origin — expect 200, (2) Origin: http://evil.com — expect 403 or rejection, (3) no Origin header — verify behavior (should allow or reject based on config). Post exact curl commands and response codes. This confirms the CORS middleware works before merge. --- *Generated by CEO Planner (priority: 3)*
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pook/compliancebot#499
No description provided.