Robin Schneider 336e666357 Add regex example to "Match detection for URIs" that is not broken (#158) ...

* Add regex example to "Match detection for URIs" that is not broken

I find it important that examples actually follow best practices. The
current regex one is not. `^https://.*google\.com$` is an improper regex
(as already pointed out because it also matches `malicious-site.com`)
that is only there to show the weaknesses of regular expressions for
this use case. I find such an example very good for this purpose but
there should also be a "good example" that complements it.

I found such a "good example" that I hope is more useful and has no
unwanted loopholes.

* Change wording from bad/good to unsafe/safe in regex match detection

* Update uri-match-detection.md

Co-authored-by: fred_the_tech_writer <69817454+fschillingeriv@users.noreply.github.com>

2021-03-03 10:49:37 -05:00

..

attachments.md

- New "Unlock w/ PIN" article + downstream re-ordering (#383)

2021-02-01 11:19:20 -05:00

authenticator-keys.md

fix (#407)

2021-02-19 11:14:04 -05:00

auto-fill-android.md

Vault Management (#382)

2021-02-01 08:58:52 -05:00

auto-fill-browser.md

Corrected spelling mistake (#409)

2021-02-19 14:34:58 -05:00

auto-fill-card-id.md

Vault Management (#382)

2021-02-01 08:58:52 -05:00

auto-fill-ios.md

Reminder to turn off iCloud Keychain (#332)

2021-02-25 09:34:24 -05:00

custom-fields.md

Addressed Issues (#431)

2021-02-25 09:13:24 -05:00

favorites.md

Vault Management (#382)

2021-02-01 08:58:52 -05:00

fingerprint-phrase.md

Vault Management (#382)

2021-02-01 08:58:52 -05:00

folders.md

Addressed Issues (#431)

2021-02-25 09:13:24 -05:00

reports.md

- New "Unlock w/ PIN" article + downstream re-ordering (#383)

2021-02-01 11:19:20 -05:00

searching-vault.md

fixes & additions (#405)

2021-02-17 12:01:54 -05:00

uri-match-detection.md

Add regex example to "Match detection for URIs" that is not broken (#158)

2021-03-03 10:49:37 -05:00