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

Issue 731259 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Handle IPPS like most printer manufacturers

Project Member Reported by skau@chromium.org, Jun 8 2017

Issue description

According to the RFC on IPPS, https://tools.ietf.org/html/rfc7472#page-10, the port for IPPS is supposed to be 631.  However, when encountering actual implementations by printer manufacturers IPPS is on port 443 which is the HTTPS port.

To align our implementation with what is most likely to work, configure IPPS printers with an explicit port number.

Also, add a note to the support documentation declaring what we're doing since it deviates from the RFC.
 

Comment 1 by adlr@chromium.org, Jun 8 2017

Should we add a port option in the setup dialog?

Comment 2 by skau@chromium.org, Jun 8 2017

We already accept ports in the dialog if you specify it in the address.

So if your IP is 192.168.1.5
And your port is 2244

Then in address, you would enter:
192.168.1.5:2244

I've avoided adding a separate field as most users won't need it and I'd like to avoid the confusion if possible.

Comment 3 by skau@chromium.org, Dec 5 2017

Labels: -Pri-1 Pri-3
Status: Available (was: Untriaged)
Since we have autodiscovery working, this is less critical.  Most IPPS setups appear to be configured correctly.

Comment 4 by skau@chromium.org, Dec 5 2017

Cc: skau@chromium.org
Owner: ----
Project Member

Comment 5 by sheriffbot@chromium.org, Dec 6

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
It doesn't seem like anybody really cares about this so marking as WontFix.  Will revisit if it is identified as an issue.

Sign in to add a comment