Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong user agent header in shutdown request #6662

Closed
mzedeler opened this issue Nov 20, 2018 · 2 comments
Closed

Wrong user agent header in shutdown request #6662

mzedeler opened this issue Nov 20, 2018 · 2 comments
Labels

Comments

@mzedeler
Copy link

Meta -

OS: Ubuntu Linux 18.x
Selenium Version: Latest available revision on master: cb8aa77
Browser: Chrome
Browser Version: 70.x
Driver variant: Ruby

Expected Behavior -

When the Selenium driver shuts down, it should send a shutdown request with User-Agent: selenium/<version>.

Actual Behavior -

When the Selenium driver shuts down, it sends a shutdown request with User-Agent: Ruby.

Steps to reproduce -

I haven't been able to write one. Will provide if anyone is interested, but I believe that I have found the specific line where the user agent isn't being set correctly:

https://github.com/SeleniumHQ/selenium/blob/master/rb/lib/selenium/webdriver/common/service.rb#L128

@barancev barancev added the C-rb label Dec 10, 2018
@twalpole
Copy link
Contributor

Before I work on this, where is the requirement for the user agent specified? I know it was added for remote connections, but I don't find anywhere that it's specified for local services.

@mzedeler
Copy link
Author

The reason that I requested this, is because if you run Selenium in an environment where other HTTP calls needs to be intercepted by mock frameworks, it is really useful to be able to white list the Selenium user agent, so it is always passed through.

At the moment, I have to use two specific white list rules, one that passes requests through if they match the Selenium user agent and another just for the shutdown request.

@p0deje p0deje closed this as completed in 8389311 May 3, 2019
@lock lock bot locked and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants