Closed jthomas closed 8 years ago
Closing as not open-source related.
@jthomas did you find a solution to this?
Sorry to bother you, I found the issue by reviewing the response content. I had missed part of the URL. The logging of the bad cookie was also seen, but was unrelated.
Environment details:
OpenWhisk on IBM Bluemix (US-South).
Steps to reproduce the issue:
Using the Apache HTTP Client to talk to the platform API, I noticed this line in the logs....
Looking at the HTTP response headers to a sample request, the cookie returned has a domain that does not match the request domain.
*The
Domain
attribute matches .whisk.ng.bluemix. We sent the request to openwhisk.ng.bluemix.net**Is this a bug?