fix: Support Content-Type: application/json and Resolve CORS Issues in Form Submission Endpoint - Githubissues

seangray-dev / formail-app

Formail offers a streamlined approach to form management, enabling instant notifications and dynamic data handling without pre-structured forms. Ideal for developers, small businesses, and anyone needing efficient form submission management, Formail simplifies the process, making it accessible and user-friendly.

https://www.formail.dev

MIT License

1 stars 0 forks source link

fix: Support Content-Type: application/json and Resolve CORS Issues in Form Submission Endpoint #54

Closed seangray-dev closed 5 months ago

seangray-dev commented 6 months ago

Description

We are experiencing issues with submitting forms when the Content-Type is set to application/json. Despite setting the appropriate CORS headers in next.config.mjs, requests from the client are blocked due to CORS policy.

Expected Behavior

When submitting data to /submit/:formId with Content-Type: application/json, the server should accept the data without any CORS errors.
The server should correctly parse JSON formatted data and respond appropriately.

Current Behavior

Fetch requests with Content-Type: application/json are failing with a CORS policy error.
- The browser console logs the error: Access to fetch at 'https://formail.dev/submit/j571gwa7mjbv1d4yj1amqw8mxs6rfrvm' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Steps to Reproduce

Set up a form submission using fetch with headers set to Content-Type: application/json.
Attempt to submit the form to the endpoint.
Observe the CORS policy error in the browser's developer console.

seangray-dev commented 6 months ago

Also need to add new example page to the docs