Hi everyone..

We have run into a little annoying thing here that we are trying to get our heads around. We are running API Connect 10.0.5 on kubernetes so Datapower is 10.5.0.7.

The situation is that our Datapower API Gateway is mirroring the HTTP request headers in the response.. We are "handling" this during normal operations in a post assembly where a simple script are removing all the request headers from the message context. It works fine.

Except for CORS preflight calls - whenever a CORS preflight call (OPTIONS) call are handled by the gateway - the global policy is parsed but assembly actions are not executed.

IBM Support asks us to try removing the headers in a post-error global policy instead (in the finally block). Super - we tried that, and the result is the same. Everything works for all requests except OPTION calls. It looks like as soon as the api-cors assembly have been running, all other assembly actions are ignored. both normal post assemblies and post-error assemblies. Even the debug information in Datapower shows it - with non-CORS calls, it shows a simple example setting a response header being executed in the final block of the post-error handling, with a CORS call, it shows that the assembly is there but does not execute it..

We are confused. Guessing we cannot be the only ones with this "issue", he he..  So we are guessing it could be a simple configuration setting, error or something along that way..

We will take any and all input/thoughts/laughs/kicks  :-) Anything 

Thanks in advance.