Message309076
I straced both chromium and Python during the issue and seen this:
Chromium open a socket (port 55084), sends "GET /domain1.html" to it.
Python accepts it, reads "GET /domain1.html", replies, OK
Chromium closes socket on port 55084
Chromium opens three sockets:
- port 55086
- port 55088
- port 55090
Python accepts a socket on port 55088 and read on it (blocking)
Chromium writes "GET /domain2.html" on socket on port 55090
At this point we're stuck, three socket are opened, Python is reading on one of them, Chromium is writing on another. |
|
Date |
User |
Action |
Args |
2017-12-27 09:33:28 | mdk | set | recipients:
+ mdk, paul.moore, ronaldoussoren, tim.golden, ned.deily, v+python, martin.panter, zach.ware, steve.dower, mattpr, rogerwang |
2017-12-27 09:33:27 | mdk | set | messageid: <1514367207.78.0.213398074469.issue31639@psf.upfronthosting.co.za> |
2017-12-27 09:33:27 | mdk | link | issue31639 messages |
2017-12-27 09:33:27 | mdk | create | |
|