Chrome regex not working correctly
Article ID: 413775
Updated On:
Products
Issue/Introduction
Proxy policy in place to only allow certain versions of Chrome and Edge browsers.
Proxy admin regex policy in proxy to allow only specified versions of chrome and edge using following CPL:
<Proxy>
request.header.User-Agent.regex="Gecko\) Chrome\/140\.0\.7339\.(18[6-9]|19\d|[2-9]\d\d) Safari\/\d+(\.\d+)" allow
request.header.User-Agent.regex="Gecko\) Chrome\/140" force_deny
When testing with Chrome version 140.0.7339.186 and above, the user was blocked instead of allowed through.
Environment
ProxySG.
Chrome browsers.
Cause
Browser setup not sending the correct user-agent string.
Resolution
Make sure the Chrome 'Network conditions' does NOT have the User-Agent 'Use browser default' flag enabled, as shown below.
When this is enabled, the default Chrome User-agent string is sent with the string 'like Gecko) Chrome/140.0.0.0' which did not match our allow rule.
Additional Information
curl can be used to inject the User-agent string for testing and can be used to confirm all works as expected.
Feedback
