Closed schallinterferenz closed 2 years ago
Hello,
I don't believe there is any way I can reproduce this, so i made a best guess. I found where the cookies should be stored once you login and copied it to all services used. From testing i can see that i found something cookie related, but it seems empty: I'm unfamiliar with how that load balancer works (does it add a cookie?) so it is hard to say if this works. But please let me know. The sessions id was already shared and should be correct for all outgoing calls.
Hello jesper,
Thank you for the quick response. Do I have to specify, define or pass the cookies somewhere, after you updated the lib?
Hi,
I expected the cookies to be assigned to the first call (logging in) and took them from there. (see https://github.com/jesper-raemaekers/python-polarion/commit/dffa8ad126a4e3054b6694aff68007b1326cb98b#diff-9e4a1f402680e813c78e2a66d9b8b7ff039fa510dac419d880a8968327ce3ab8R92 ) But it seems i might misunderstand, you want to specify a cookie? How do you create this?
I have to excuse for the confusion. You have understood my issue right!
It works like a charm :) Tested it five time. No errors at all. It finds the project instantly and our load balancer gets the right cookies.
Thanks a lot!
When do you think you will release a update?
It was released today with version 0.4.0
Thanks a lot!
Hello,
We have a 2 server setup for Polarion in AWS, and the 2 servers run behind a load balancer. The problem we encounter is that it happes often that we authenticate on one of the servers, and the next request goes to the other server and we get the following error:
My question now is, how I can pass the transport cookiejar, as well as the session id, via the library, so that our load balacer knows where to route the request?