Open titusfortner opened 2 weeks ago
Default Http Client added separate timeout values for open and read timeouts, since that conflicted with the superclass timeout setting, we removed that setting (https://github.com/SeleniumHQ/selenium/commit/2965e4e0fa6981ca2fe329ea944c5f3acd0b1caa)
timeout
We removed/deprecated the persistent client subclass, but not the curb client subclass. So curb client can no longer set timeouts.
Selenium::WebDriver::Remote::Http::Curb.new(timeout: 120)
n/a
Ruby trunk
no
What happened?
Default Http Client added separate timeout values for open and read timeouts, since that conflicted with the superclass
timeoutsetting, we removed that setting (https://github.com/SeleniumHQ/selenium/commit/2965e4e0fa6981ca2fe329ea944c5f3acd0b1caa)We removed/deprecated the persistent client subclass, but not the curb client subclass. So curb client can no longer set timeouts.
How can we reproduce the issue?
Relevant log output
Operating System
n/a
Selenium version
Ruby trunk
What are the browser(s) and version(s) where you see this issue?
n/a
What are the browser driver(s) and version(s) where you see this issue?
n/a
Are you using Selenium Grid?
no