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

Force BrowserMobProxy and Selenium Chrome Driver to use QUIC #60

Closed
SivaKesava1 opened this issue Oct 26, 2016 · 3 comments
Closed

Force BrowserMobProxy and Selenium Chrome Driver to use QUIC #60

SivaKesava1 opened this issue Oct 26, 2016 · 3 comments

Comments

@SivaKesava1
Copy link

Hi all,
I am working on downloading HAR from Chrome for YouTube through Selenium Python Script.
Code Snippet:

            chrome_options = webdriver.ChromeOptions()
        chrome_options.add_argument("--proxy-server={0}".format(url))
    chrome_options.add_argument("--enable-quic")

        self.driver = webdriver.Chrome(chromedriver,chrome_options = chrome_options)

           self.proxy.new_har(args['url'], options={'captureHeaders': True})   // BrowserMobProxy
       self.driver.get(args['url'])
           result = json.dumps(self.proxy.har, ensure_ascii=False)

I want QUIC to be used whenever I download HAR but when I look at the packets through Wireshark Selenium driver is using TCP only . Is there a way to force BrowserMobProxy and Chrome Driver to use QUIC?

@AutomatedTester
Copy link
Owner

I dont know what QUIC is.

Selenium uses HTTP to send commands between the client and the remote end so natually uses TCP.

@SivaKesava1
Copy link
Author

But Selenium Webdriver has Chrome Options to which an argument like 'Enable QUIC' can be added.So if anyone else have an idea about this please comment.

@AutomatedTester
Copy link
Owner

I suggest raising this with the ChromeDriver folk Or you can send questions to the selenium user group

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants