I am able to see non-whitelisted headers but I'm only see bearer-token for example. Cookies are always override.
It feels like chrome custom tab is blocking our cookies sent with extra-headers.
I am using the example code with our domain that is validating correctly the digital asset links for relation use as origin.
On requests headers I can see bearer-token correctly but cookie has other stuff and does not contain the ones I'm sending.
Is there a chance that we cannot override/add more cookies sent by the server, from the app?
Like if we already have cookie: "something=123;" we cannot add (or override) cookies from the app and end up with something like cookie: "something=123; sendFromApp=newCookie;"?
Describe the bug
I am able to see non-whitelisted headers but I'm only see
bearer-tokenfor example. Cookies are always override.It feels like chrome custom tab is blocking our cookies sent with extra-headers. I am using the example code with our domain that is validating correctly the digital asset links for relation use as origin.
On requests headers I can see bearer-token correctly but cookie has other stuff and does not contain the ones I'm sending.
Is there a chance that we cannot override/add more cookies sent by the server, from the app?
Like if we already have
cookie: "something=123;"we cannot add (or override) cookies from the app and end up with something likecookie: "something=123; sendFromApp=newCookie;"?