apac.ehssrisk.sai360.net - Firefox is unsupported
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P3, Webcompat Score:2, firefox143 affected, firefox144 affected, firefox145 affected)
People
(Reporter: rbucata, Assigned: twisniewski)
References
(Depends on 1 open bug, )
Details
(5 keywords, Whiteboard: [webcompat-source:web-bugs][webcompat:diagnosis:ua-sniffing])
User Story
user-impact-score:20 platform:windows,mac,linux,android impact:blocked configuration:general affects:all branch:release diagnosis-team:webcompat
Attachments
(1 file)
Environment:
Operating system: Windows 10
Firefox version: Firefox
Steps to reproduce:
- Navigate to: https://apac.ehssrisk.sai360.net/fisherandpaykel/
- Observe
Expected Behavior:
Page loads
Actual Behavior:
Browser unsupported
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
Created from https://github.com/webcompat/web-bugs/issues/180748
| Reporter | ||
Updated•10 months ago
|
Comment 1•10 months ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Updated•10 months ago
|
Comment 2•10 months ago
|
||
Seems to work with Chrome Mask.
| Assignee | ||
Updated•10 months ago
|
Updated•10 months ago
|
| Assignee | ||
Comment 3•10 months ago
|
||
Updated•10 months ago
|
Comment 5•10 months ago
|
||
| bugherder | ||
| Assignee | ||
Updated•10 months ago
|
Updated•10 months ago
|
Comment 6•9 months ago
|
||
This is just server-side sniffing, at the HTTP-request level.
With the intervention disabled, "copy-as-cURL" gives me this command:
curl 'https://anz4.ehssrisk.com/fisherandpaykel/' \
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:146.0) Gecko/20100101 Firefox/146.0'
which gives me back the reported error-page HTML as a simple HTML doc, including:
<h2>Unsupported Browser Detected</h2>
<p>We've noticed you are using an unsupported browser. Please switch to a modern browser to use SAI360.</p>
Whereas if I use the User Agent string that we've got from the intervention...
curl 'https://anz4.ehssrisk.com/fisherandpaykel/' \
-H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:146.0) Gecko/20100101 Firefox/146.0 AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36'
... I get back HTML for the actual webapp with scripts etc.
--> Removing webcompat:needs-diagnosis; there's no bug to diagnose here, other than this server-side UA sniffing.
Updated•9 months ago
|
Updated•6 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
Description
•