acceptInsecureCerts capability is ignored

[ghostwords]

Setting acceptInsecureCerts to False is ignored by geckodriver. The same pattern works with ChromeDriver.

We need to disable acceptInsecureCerts in order to better simulate an actual person's experience browsing the Web. (People are unlikely to go past insecure cert warnings.)

In the following example, the unhandledPromptBehavior setting is respected, while acceptInsecureCerts remains set to True.

            caps = DesiredCapabilities.FIREFOX.copy()
            caps['acceptInsecureCerts'] = False;
            caps['unhandledPromptBehavior'] = "ignore";

            self.driver = webdriver.Firefox(firefox_profile=profile,
                                            firefox_binary=self.firefox_path,
                                            options=opts,
                                            desired_capabilities=caps,
                                            service_log_path=os.path.devnull)

(The above code is from badger-sett/crawler.py)

I originally filed this as mozilla/geckodriver#1718.

System

• Version: 0.26.0
• Platform: Ubuntu Linux 16.04
• Firefox: 75
• Selenium: Python bindings version 3.141.0

[ghost]

👋 Hi there! Thank you for creating this issue.

I am the Selenium Assistant Bot 🤖, I triage issues in this repository. If I can't do it, I label it to help maintainers identify issues that need triaging.

I am an Open Source project 🙌, post bugs or ideas here!

[ghost]

❗️ It seems this issue is not using any of the supported templates

💡 Supported issue types are (they start with):

• 🐛 Bug Report (bugs found in a recent release)
• 🚀 Feature Proposal (a useful feature you would like to propose)
• 💥 Regression Report (a supported feature is not working anymore)

Issue templates help this project to stay in shape, please use them and fill them out completely. By doing that you are helping the project because the community and maintainers can provide prompt feedback, and potentially solve the issue.

If you are asking a question, a better way to address this is:

• 📫 Send questions and support requests to the Selenium user group
• 📮 Post them to StackOverflow
• 🗣 Join us in the IRC/Slack channel where the community can help you as well

If you think this is incorrect, please feel free to open a new issue.

Thank you for your contributions.

[ghostwords]

"Thank you for your contributions."

[AutomatedTester]

In future please don't delete the template and just follow the questions in the bug.

[AutomatedTester]

looking into this, Firefox is doing the right thing.

If you start using the *Options classes, which is the preferred way, this would have worked. Will rework the code that if it sees this to call the options instead.

[ghostwords]

Thank you for looking into this, and for suggesting to stop using DesiredCapabilities.

Since DesiredCapabilities is deprecated, should users of up-to-date bindings see deprecation warnings?