New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 801321 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 793066
Owner:
Last visit > 30 days ago
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug
Proj-Servicification

Blocking:
issue 721401



Sign in to add a comment

Avoid socket limits in proxy_resolving_client_socket_factory.cc

Project Member Reported by xunji...@chromium.org, Jan 11 2018

Issue description

This is to follow up a review comment in https://chromium-review.googlesource.com/c/chromium/src/+/860198/9/net/socket/client_socket_pool_manager.cc#409 .

proxy_resolving_client_socket_factory.cc currently uses net::InitSocketHandleForRawConnect() which is subject to the "6 sockets per origin" socket limit. We want to get rid of this socket limit for this type of sockets.

Using LOAD_IGNORE_LIMITS might work. However, there is a check in client_socket_pool_base.cc which asserts that LOAD_IGNORE_LIMITS is only used with MAXIMUM_PRIORITY. We can't hard code request priority to MAXIMUM_PRIORITY, because it will affect HostResolver requests which uses the priority.


Filing a bug to figure out what to do here.




 
Cc: mmenke@chromium.org
Mergedinto: 793066
Status: Duplicate (was: Assigned)

Sign in to add a comment