When `<FaultResponse><Copy><Headers>` is used in a raisefault policy in order to copy response headers from the source to the error message, set-cookie headers are broken when they have an `expires` directive containing a comma (e.g. 'expires=Fri, 30-Dec-16 16:23:42 GMT;').
These are the headers sent from the target:
Set-Cookie: A=B; expires=Sun, 29-Jan-2017 17:04:37 GMT; Path=/
Set-Cookie: C=D; expires=Fri, 27-Jan-2017 17:04:37 GMT; Path=/
Set-Cookie: E=F; expires=Wed, 25-Jan-2017 17:04:37 GMT; Path=/
But when these set-cookie headers are copied as described above, they are returned in the response like this:
Set-Cookie: A=B; expires=Sun
Set-Cookie: 29-Jan-2017 17:04:37 GMT; Path=/
Set-Cookie: C=D; expires=Fri
Set-Cookie: 27-Jan-2017 17:04:37 GMT; Path=/
Set-Cookie: E=F; expires=Wed
Set-Cookie: 25-Jan-2017 17:04:37 GMT; Path=/
This seems to be related to the way the apigee platform breaks set-cookie headers as has been documented in the following posts:
https://community.apigee.com/questions/6587/modify-set-cookie-header-addchange-in-javascript.html
https://community.apigee.com/questions/1908/question-about-accessing-all-set-cookie-values-fro.html
Is there any way to work around this apigee bug?
LinkedIn
Twitter
