ericmckean / chromedriver

Automatically exported from code.google.com/p/chromedriver
0 stars 0 forks source link

chromedriver does not close connection after sending response #1001

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Issue Description:
chromedriver does not close http connection after sending the response. 
This leads to clients hanging waiting for the connection to close.
In my case it's cpp-netlib that does not work with chromedriver.

Steps to reproduce:
1) take the http client example from cpp-netlib
http://cpp-netlib.org/0.11.0/examples/http/http_client.html
2) start chromedriver
3) call the status request
 ./http_client http://localhost:9515/status

Original issue reported on code.google.com by speedpa...@gmail.com on 11 Dec 2014 at 6:11

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago

use http://localhost:9515/status  as URL with any browser (Chrome, IE, Firefox)
you can see HTTP response 
{"sessionId":"","status":0,"value":{"build":{"version":"alpha"},"os":{"arch":"x8
6_64","name":"Windows NT","version":"6.1 SP1"}}}

I tried all three,  and none of them  hanging.

Original comment by andrewch...@chromium.org on 1 Jan 2015 at 12:03

GoogleCodeExporter commented 9 years ago
the problem is the combination of cpp-netlib (http://cpp-netlib.org) and 
chromedriver.
I'm using cpp-netlib in my seleniumcpp library project 
(https://bitbucket.org/speedpat/seleniumcpp).

up to chromedriver v2.9 everything used to work correctly, since chromedriver 
v2.10, cpp-netlib hangs waiting for the connection to be closed.

Original comment by speedpa...@gmail.com on 1 Jan 2015 at 7:46

GoogleCodeExporter commented 9 years ago

Original comment by samu...@chromium.org on 21 Feb 2015 at 12:18