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

Issue 688050 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Port Forwarding is restricted to 1024..10000

Reported by aml...@gmail.com, Feb 2 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0

Steps to reproduce the problem:
1. Enable remote debugging
2. Add a forwarding rule for a port beyond 10000
3. Connect the device

What is the expected behavior?
Forwarding is enabled as it happens with the range < 10000

What went wrong?
The port number is displayed with a red circle and it states that there's an error

Did this work before? No 

Chrome version: 56.0.2924.76 beta (64-bit)  Channel: beta
OS Version: 10.0
Flash Version: 

In https://bugs.chromium.org/p/chromium/issues/detail?id=322245 the range of ports was expanded, but as the comment #5 explains, Visual Studio uses the range 44300-44399 for local SSL, so it's not possible to even try to debug such sites with remote debugging.

 
Owner: eostroukhov@chromium.org
Labels: Needs-Triage-M56
Labels: -Needs-Triage-M56 TE-NeedsTriageHelp
Adding TE-NeedsTriageHelp label, as it is out of TE-scope.

Thanks...!!
Labels: -TE-NeedsTriageHelp Needs-Feedback
Status: Assigned (was: Unconfirmed)
I am unable to reproduce the issue. Can you clarify the step 2? Are you using chrome://inspect page or the DevTools (devtools are opened by pressing the F12).

Comment 5 by aml...@gmail.com, Mar 14 2017

I usually open inspect from the DevTools, but chrome://inspect shows the same problem. I'll attach some pictures
devtools config.png
14.5 KB View Download
devtools connection.png
11.2 KB View Download
chrome inspect.png
17.3 KB View Download
Project Member

Comment 6 by bugdroid1@chromium.org, Oct 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9b267445180d7d61b94775d3cb4ca283006ec114

commit 9b267445180d7d61b94775d3cb4ca283006ec114
Author: Eugene Ostroukhov <eostroukhov@chromium.org>
Date: Tue Oct 24 01:58:06 2017

[DevTools] Allow forwarding ports 32768-65535

Bug:  688050 
Change-Id: I8daaf789c48710e91cb32c05ddf77ee261419c13
Reviewed-on: https://chromium-review.googlesource.com/731505
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Eugene Ostroukhov <eostroukhov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#511005}
[modify] https://crrev.com/9b267445180d7d61b94775d3cb4ca283006ec114/content/browser/devtools/protocol/tethering_handler.cc

Status: Fixed (was: Assigned)
Fix was published to Chrome. I am not sure when it will be available in Chrome Android.

Sign in to add a comment