Correct Net::HTTP::Persistent bug when using newer versions #8387
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for contributing to Selenium!
A PR well described will help maintainers to quickly review and merge it
Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.
Description
Fix the integration with the Net HTTP Persistent Gem.
Motivation and Context
The default Net::HTTP Library allows the end user to force SSL using the
use_ssl=
method. Net::HTTP::Persistent doesn't in newer releases. This causes errors to be thrown when using the Net::HTTP::Persistent shim.This change moves SSL configuration into its own method, allowing the shim to handle this for different versions while keeping the default HTTP code clean.
Types of changes
Checklist