RequestPolicy/requestpolicy — Issue #104: Full Address Strictness Setting -- honors only non-standard ports? (or hides default ports?)
Author: jsamuel
Created: 2011-12-22 18:52:44+00:00
State: open
Labels: extension

imported trac ticket
created: 2010-05-11 00:37:09
reporter: eibwen

Strictness setting states:
* Full address (!http://www.requestpolicy.com:81)

However, context menu items to generate whitelist policies as well as whitelist entries generated with this setting appear without the port as:

!http://www.requestpolicy.com
!https://www.requestpolicy.com

As opposed to (with the port):

!http://www.requestpolicy.com:80
!https://www.requestpolicy.com:443

This is inconsistent with the setting description, and is ambiguous whether the port is being honored as part of the full address specification . Granted, above are the default ports for the respective protocols; however, the questions then become whether the typical user expected to know that:

* Those ports are defaults for the respective protocols
* The default ports are honored, but are not shown

Granted, Firefox itself uses the default ports if omitted, and will actually remove explicitly typed default ports from the address...

As such, current behavior is consistent with Firefox behavior; however, it is inconsistent with setting description.

Recommend clarification of setting description accordingly.