fix: match allowed regex fully

[jmattheis]

Fixes #1052

[eternal-flame-AD]

Lgtm.

Also, I think a simpler solution is simply prepend/append a ^ and $ to the regex if it's not already there.

Ad a side note, I honestly didn't understand why this is strictly needed. I agree with the original issue that it seems like WebSocket won't be a viable cross origin attack vector (does not eliminate the need to exfiltrate token).

[jmattheis]

I see this more as a fix to make the setting behave as expected (must match the string fully). I'd say the current docs and issues seem to imply this.

I'll change it to wrap the user regex into "^(?:"+userregex+")$". So we don't need the longest() and stringindex stuff.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.09%. Comparing base (e6361ca) to head (8f2dad9).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1054      +/-   ##
==========================================
- Coverage   76.16%   76.09%   -0.07%     
==========================================
  Files          66       67       +1     
  Lines        3625     3619       -6     
==========================================
- Hits         2761     2754       -7     
- Misses        653      654       +1     
  Partials      211      211              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.