URI match detection for ports

grb · May 17, 2024, 4:48pm

I would suggest reporting this as an Issue on GitHub. There is a possibly related issue with local domains already reported here:

github.com/bitwarden/clients

Local TLDs are matched on “Base Domain” rule

opened 05:42PM - 12 Mar 24 UTC

piotr-dobrogost

bug browser

### Steps To Reproduce 1. Set _Default URI match detection_ to _Base domain_. …2. Define login item with urls http://localhost/, http://domainx.company.local/, http://domainy.company.local/, all set to _Default match detection_. 3. Open url http://logstash.test.company.local/ ### Expected Result Login item defined in step2 should **not** be matched. ### Actual Result Login item defined in step2 **is** matched. ### Screenshots or Videos _No response_ ### Additional Context This is contrary to the the following [note](https://bitwarden.com/help/uri-match-detection/#base-domain) from docs (emphasis mine): > Note > Login items intended to auto-fill in a URI with a **local TLD** (e.g. http://mysite.local or https://mysite.lan) or single-term hostname (e.g. http://localdevice) **will not be available for base domain detection**. We recommend using [host matching](https://bitwarden.com/help/uri-match-detection/#host). I described this problem originally at https://community.bitwarden.com/t/login-items-with-local-tld-matched-according-to-base-domain-rule-contrary-to-the-information-in-the-docs/64419 ### Operating System Linux ### Operating System Version Fedora 39 ### Web Browser Chrome ### Browser Version _No response_ ### Build Version Version 121.0.6167.160 (Official Build) (64-bit) ### Issue Tracking Info - [ ] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

The above issue was also discussed previously on the Community Forum, here: