bitwarden/help
1
0
Fork 0
mirror of https://github.com/bitwarden/help synced 2025-12-06 00:03:30 +00:00
Code Issues Releases Wiki Activity

Fix URI vault regex example (#393)

Browse Source 
I find it important that examples actually follow best practices. The
current regex does not escaping dots in URIs when writing regex is a
mistake that is often made, even by advanced regex people. I think this
comes from the way we humans look at URIs. Dots are so common in there,
aren’t they?  Yes, but we write proper regular expressions here, not
something in between.

Updates: #41
Alternative: #158
Replaces: #160
This commit is contained in:
Robin Schneider
2021-02-10 20:59:51 +01:00
committed by GitHub
parent 93d279f36b
commit 2b9d4c66e6
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
_articles/features/uri-match-detection.md
View File

@@ -75,7 +75,7 @@ Regular expressions are an advanced option and can be quite dangerous if used in
Selecting **Regular expression** will prompt Bitwarden to offer auto-fill when the detected resources matches a specified [regular expression](https://en.wikipedia.org/wiki/Regular_expression){:target="_blank"}. Regular expressions are always *case insensitive*.
For example, if the URI vault `^https://.*google.com$` uses regular expression match detection:
For example, if the URI vault `^https://.*google\.com$` uses regular expression match detection:
- **Auto-fill offered** for `https://google.com`, `https://sub.google.com`, `https://malicious-site.com?q=google.com`
- **Auto-fill not offered** for `http://google.com` or `https://yahoo.com`