fix(hub/cors): allow PATCH in preflight Access-Control-Allow-Methods
Browser CORS preflight (OPTIONS) for PATCH /campaigns/:id was rejected because PATCH wasn't listed in Access-Control-Allow-Methods. The browser surfaced this as a generic "Load failed" on the "Enregistrer" button of the edit-params dialog. curl bypasses CORS so backend testing missed it. The header now includes PATCH alongside GET/POST/PUT/DELETE/OPTIONS. Verified live: OPTIONS preflight now returns the full method list. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
parent
89057d0166
commit
c55f75739f
|
|
@ -39,7 +39,7 @@ const server = http.createServer(async (req, res) => {
|
|||
const method = req.method
|
||||
|
||||
res.setHeader('Access-Control-Allow-Origin', '*')
|
||||
res.setHeader('Access-Control-Allow-Methods', 'GET, POST, PUT, DELETE, OPTIONS')
|
||||
res.setHeader('Access-Control-Allow-Methods', 'GET, POST, PUT, PATCH, DELETE, OPTIONS')
|
||||
res.setHeader('Access-Control-Allow-Headers', 'Content-Type, Authorization, X-Authentik-Email, X-Authentik-Groups')
|
||||
if (method === 'OPTIONS') { res.writeHead(204); return res.end() }
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user