Skip to content

Remove Content-Type header#188

Closed
ascibisz wants to merge 1 commit intomainfrom
fix/cors-header-error
Closed

Remove Content-Type header#188
ascibisz wants to merge 1 commit intomainfrom
fix/cors-header-error

Conversation

@ascibisz
Copy link
Copy Markdown
Contributor

Problem

Right now on staging, we're getting this CORS error:
Screenshot 2026-04-14 at 9 32 44 AM

Solution

What I really want to do is go in to AWS API Gateway and adjust the CORS policy to allow for the Content-Type header, but everytime I do that I get a "network error" and it won't go through. I vaguely remember it being tricky to adjust the CORS policy previously, perhaps due to my lack of AWS permissions, although that's not indicated based on the error message, so I'm not really sure.

Technically, the Content-Type header is optional in this case, so it seems fine to just pull it out from the request itself? This did seem to resolve the problem for me.

@github-actions
Copy link
Copy Markdown

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 32.51% 679 / 2088
🔵 Statements 32.51% 679 / 2088
🔵 Functions 39.42% 41 / 104
🔵 Branches 73.3% 151 / 206
File Coverage
File Stmts % Branch % Funcs % Lines Uncovered Lines
Changed Files
src/App.tsx 0% 0% 0% 0% 1-7, 16-21, 23, 25-27, 29-41, 43, 45-47, 49-55, 57-71, 73-90, 92-100, 102-121, 125, 127-146, 148-153, 155-163, 165-170, 172-184, 186-191, 193-200, 202-213, 215, 217
Generated in workflow #259

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 14, 2026

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-04-15 20:19 UTC

@ascibisz ascibisz closed this Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant