We have this necessity to have all the requests (via two different endpoints) relating to the same user to be directed to the same pod. Ideally, it'd be something like Sticky Sessions but with the identifier supplied in a header, instead of using cookies. Is there a way to achieve this?
If not and if we use Sticky sessions instead (making it thus all about the session and not the related user), how do you suggest I go about with the API endpoint requests then? Good thing is the API endpoint requests are only considered once there's at least one browser connection for the related user, so the cookie can be communicated to the client API before it makes its first request for the related user/session.
Thanks
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Daniele,
We have this necessity to have all the requests (via two different endpoints) relating to the same user to be directed to the same pod. Ideally, it'd be something like Sticky Sessions but with the identifier supplied in a header, instead of using cookies. Is there a way to achieve this?
If not and if we use Sticky sessions instead (making it thus all about the session and not the related user), how do you suggest I go about with the API endpoint requests then? Good thing is the API endpoint requests are only considered once there's at least one browser connection for the related user, so the cookie can be communicated to the client API before it makes its first request for the related user/session.
Thanks