- From: roryhewitt <notifications@github.com>
- Date: Wed, 04 May 2016 10:46:00 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc:
- Message-ID: <whatwg/fetch/pull/293/c216945168@github.com>
@annevk, what you have done is great, but I'd love to see some real user examples (from both a client and server perspective. The data in this document is great, but its understandably from a browser developer perspective, so it uses terminology that a client-side (JavaScript) developer or a server-side developer may not understand. Attached is a document (*CORS request processing - Simple*) I wrote which explains (to a client-side developer) what they need to do, if anything, related to CORS, depending on their requirements. As such, it doesn't refer to e.g. "credentials mode", but instead refers to the "withCredentials" flag that an end-user would see in their JavaScript. I thought I had a separate document referencing 'complex' CORS (including the preflight OPTIONS request), but I can't find it right now, but I can always write it. I don't know if examples like this could be included _somewhere_ in the WHATWG ecosphere - perhaps not directly in the fetch standard, but maybe referenced in there? There's also a separate PowerPoint presentation about CORS which explains it (as best I can) to other technical people - that's just for 'fun'... [CORS Overview.pptx](https://github.com/whatwg/fetch/files/249276/CORS.Overview.pptx) [CORS request processing - Simple.docx](https://github.com/whatwg/fetch/files/249265/CORS.request.processing.-.Simple.docx) --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/293#issuecomment-216945168
Received on Wednesday, 4 May 2016 17:48:45 UTC