Solution option - pass through to the app

[ijmitch]

Just for completeness, I'll describe another option...

What if we decided that handling an OPTIONS request was just another obligation for the app? It would have to be opted into via a URIMAP option (handleoptions?), but once opted into then the app could do EXEC CICS WEB EXTRACT HTTPMETHOD in order to distinguish OPTIONS from GET, POST etc.

[ijmitch]

Is this something an app should be asked to do?

[Karagines]

CORS falls into the security realm controlling what can be accessed from where. In the examples given in the other threads, the configuration is outside of the application. I believe the server should support CORS in its configuration. If the application wants to take on this responsibility, the server can allow it (say through handleoptions in a URIMAP).

[ijmitch]

Thanks @Karagines - I'll take that as a possible option after first preference that this is handled as configuration separate from the application.

[RussTeubner]

Hi Ian, First, thanks for your work on this matter. What is the current state of your thinking/plans? For me at this juncture, the division of labor between application and server is unimportant (although i do appreciate the importance of getting that division correct ultimately). What is the clearest path to get my code handing OPTIONS? Thanks, Russ Russ Teubner, CEO HostBridge Technology russ@hostbridge.com 1 405 747 7877 (c) 1 405 533 2950 (w) (Sent from my iPad with a tiny keyboard - enjoy) On Apr 13, 2017, at 1:37 AM, ijmitch <notifications@github.com> wrote: Thanks @Karagines <https://github.com/Karagines> - I'll take that as a possible option after first preference that this is handled as configuration separate from the application. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZEhj73N3fVJb2v4-m5YzWi4nAdkjEGtks5rvd67gaJpZM4M2tJb> .