0

I am trying to work with soap client at the browser. For that, I am using soap js client.

I tried to use soap client in the browser. Everything works fine except for session authorization. I have splitted api into 8 services. So I need to create 8 different Soap Client instances and share session between them, but I can't make it work. The weird thing is that response is returning "Set-cookie" header but browser don't write it in cookies and next Soap Client do request like from another session and gets "Set-cookie" again which is ignored again. Can somebody explain to me why it's happening? Why browser ignores "Set-cookie" in response? And if somebody knows how to deal with my problem it would be very nice to give me some advice. Thanks a lot.

Request and response headers

Cookies at localhost:3001 after successful request

Taras Halynskyi
  • 149
  • 2
  • 7
  • Can edit your question to include the `set-cookie` header? It would be helpful to see if there are any special directives like `domain`, `expires`, `secure`, etc. Feel free to redact/change the cookie value if it's sensitive. – David784 Jul 21 '19 at 13:22
  • @David784 I added screenshots with request and response headers and Browser storage after a successful request. Maybe it will help to understand the current case. Thx. – Taras Halynskyi Jul 22 '19 at 06:59
  • Thanks, I thought there might be a secure directive or something, but looks okay. the `httponly` directive means you won't be able to see the cookie from JavaScript, but you should still see it in the dev tools. That second screen shot doesn't look right to me though...that only appears to be storage size, not a cookie listing. In chrome the cookies would be listed in the dev tools, Application tab, storage section, expand the cookies subsection and choose the correct domain. – David784 Jul 22 '19 at 21:42

0 Answers0