I'm trying to use seleniumwire with the chrome webdriver to automate a task that is tedious and it seems like it's redirecting from my input of http://somesite.com:port/ to https://somesite.com:port/. When the browser opens, it gives me a 502 error, but I can then manually remove/restore to http:// and it works.
I'm revisiting old code that I hadn't finished working on but did work just fine in the past and it's only now started failing with this error.
Any ideas as to how to force the http to stick?
I found that it may not be caused by selenium, but by Chrome. An earlier Chrome version (113.x) can resolve this problem.