GoogleChrome / GoogleChrome/android-browser-helper

[Question] Share/add cookies to cookie request headers?

Open
#379 1 comment 3 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
832
Forks
370
Avg merge
1d 3h
Merged PRs (30d)
6

Description

**Describe the bug**

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.

187477668-24c47aba-f77d-46ee-95cb-309bc2acb43e

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;" `?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.