I'm working on an upgrade from CEF 88 to 104 and ran into a difference in behavior that I'm having trouble tracking down.
In my program we make a request that is not associated with a browser to download some asset. The url is http and it gets redirected to https. The server side is expecting a cookie, which does exist, but for whatever reason doesn't end up in the redirected request. We specify UR_FLAG_ALLOW_STORED_CREDENTIALS on the request. When I use the old CEF 88 build it all just works.
If I add UR_FLAG_STOP_ON_REDIRECT and manually generate another request for the redirect then the cookie is there, but since this was not necessary before I'm hesitant to make this change without fully understanding why this would be necessary now.
Just curious if anyone has any ideas on whether this is expected due to changes in Chromium or if I'm just missing something obvious.