Force browser to do a preflight

[theking2]

MDN URL

https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request

What specific section or headline is this issue about?

Suggestions for implementation

What information was incorrect, unhelpful, or incomplete?

As pre-flight requests are created 'automatically" it makes is perhaps hard on the developer to implement a correct response to exactly such a request. How should a pre-flight request be debugged?

What did you expect to see?

Some suggestions how to coerce a browser to start a pre-flight request. Or a more elaborate process flow of request, pre-flight-request. and the expected responses.

Do you have any supporting links, references, or citations?

https://reflectoring.io/complete-guide-to-cors/

Do you have anything more you want to share?

Apart from that: excellent source

MDN metadata

Page report details

• Folder: en-us/glossary/preflight_request
• MDN URL: https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/glossary/preflight_request/index.md
• Last commit: 4a9f9d2
• Document last modified: 2021-10-08T00:24:32.000Z

[Josh-Cena]

@theking2 It has been a while but I don't think the request of this issue is clear. Are you asking for advice as the implementer of client code or server code? It seems you are implementing a server that responds to preflight requests, and you want to reliably trigger preflight requests in the browser so you can test your server's responses?

I believe most existing server solutions handle preflight requests automatically without explicitly handling OPTIONS requests. We already document what headers browsers expect from the preflight response.