* enterprise policy typo
* more generic language in fido doc
* missing paren
* replace apr image with gif, profit
* fix language that ain't friendly to non-native english speakers (TY @Greenderella)
* faq item for mp hint
* windows firewall exclusion tip
* update cert article w/ powershell instructions for new letsencrypt cert
* improve collection header
* note on self-host server release lag
* duo bypass code tip
* revert
* clarification on where to find legacy mac .dmg
* tip for update email address
* code vetting security faq
* /managing-items/ refactor
* two-step login 'remember me' duration
* small updates, including denoting purpose of the globe icon
* additional tip for deleting users in a self-host org!
* uri component pieces
* encryption key edit
* importing cleanup
* notes re: importing on file attachements
* 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>
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
* Add examples to clarify Host/Regular expression
Add an example to the Host section illustrating that Host not only doesn't match parent domains but also doesn't match subdomains
Add an example to Regular expression illustrating that the example regex matches substrings of the URI (because there is no end of string character)
* Revert the regex example and change the regex
Instead of adding an example to the Regular expression section to clarify that
the regex shown doesn't require the string end in google.com, let's instead
change the regex to end in a `$` and all the existing examples make a lot more
sense.
