fun fact: User-Agent is not a forbidden request header (https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_request_header); browsers are supposed to let JS code make requests with custom User-Agent headers, and indeed Firefox (Gecko) and GNOME Web aka Epiphany (WebkitGTK) both permit this. but because Google Chrome blatantly violates the spec and has a dominant market position, everyone has to perpetually act as if setting the User-Agent request header is not possible
Conversation
Notices
-
Embed this notice
Lucas Werkmeister (lucaswerkmeister@wikis.world)'s status on Tuesday, 01-Apr-2025 22:54:47 JST Lucas Werkmeister
-
Embed this notice
Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Tuesday, 01-Apr-2025 22:55:25 JST Ryan Castellucci :nonbinary_flag:
@LucasWerkmeister unsure if being trolled
-
Embed this notice
Ryan Castellucci :nonbinary_flag: (ryanc@infosec.exchange)'s status on Tuesday, 01-Apr-2025 23:29:38 JST Ryan Castellucci :nonbinary_flag:
@LucasWerkmeister FWIW changing the user agent header does not actually obscure what the browser is.
-
Embed this notice
Lucas Werkmeister (lucaswerkmeister@wikis.world)'s status on Tuesday, 01-Apr-2025 23:29:39 JST Lucas Werkmeister
@ryanc nope, not an april fools joke. you can find the chromium bug on the linked mdn page
-
Embed this notice