Don't stop script execution on non HTTP 200

[JekRock]

Is your feature request related to a problem? Please describe.
Currently, there are services that secure website from automation tools like ferret. Some of them send 405 in response to the DOCUMENT function call that make a ferret script fail with an error even though a page is available (not the original page, but usually a page with the captcha).

Describe the solution you'd like
It would be nice to either have some kind of flag that will tell ferrret to ignore response codes and continue the script execution or to pass response codes to ignore as a parameter to the DOCUMENT function, for exemple.

Additional context
For the example with the captcha above, the script could have contunued the execution and wait for someone solving the captcha manually (in non-headless browser). It can be achieved by just calling a "wait for element" function.

[ziflex]

Hey, could you provide some links as examples?

[JekRock]

Sure. Try this one.
It will very quickly open the page with captcha when you start to do anything with the page

[ziflex]

hey, are you using CDP driver or in-memory one?
I see that Chrome handles these kind of pages.

[JekRock]

I was using the CDP driver

[ziflex]

What Chrome version?

[ziflex]

I'm trying to reproduce it with CDP driver, but it's working fine.
Could you give me more information?

[ziflex]

I added support to HTTP (InMemory) driver, but I don't see that it needs to be added to CDP.
Feel free to re-open.