The JS Bindings break after a 302 redirect

[rsc092020]

I'm not sure whether this warranted an issue or not, so I thought I would ask here first. I'm having a problem after upgrading versions from 119 to 134 where the JS bindings break after a 302 redirect. I have been able to reproduce this with my fork: https://github.com/rsc092020/CefSharp. I only added 1 commit for now, where I just added some redirect logic to the class handling the file serving, so you can also just copy paste that instead of cloning/adding a remote.

Steps:

1. Run CefSharp.WinForms.Example
2. Click Javascript Binding Tests
3. Append ?redirect=true, and hit Enter
   => Observe that the binding tests break

The first time it breaks is 7af16b9

I know from debugging that it is calling OnBrowserCreated, then OnBrowserDestroyed in the same process, which means that the bindings throw Error: BindObjectAsyncHandler::Execute - Browser wrapper null, unable to bind objects.

I'm trying to figure out if this is an actual bug or intended behavior. Also, is there any workarounds other than avoiding redirects, or not using the Chrome Runtime.

[amaitland]

The first time it breaks is 7af16b9

This changed switched from using the old Alloy Bootstrap to using the new Chrome Bootstrap. There have been many changes in behavior as a result. CEF has since removed the Alloy Bootstrap. You can read more about it here #4795

I'm trying to figure out if this is an actual bug or intended behavior.

It's probably as bug, though it will probably require changes in CEF to get working again.

When are OnContextCreated and OnContextReleased called? Can you map out the sequence of OnBrowserCreated, OnBrowserDestroyed , OnContextCreated and OnContextReleased calls

Once we've collected enough information, someone will need to raise at issue at https://github.com/chromiumembedded/cef/issues

[amaitland]

Can you try disabling the BF cache.

settings.CefCommandLineArgs.Add("disable-back-forward-cache");