News for hackers. Stuff that matters.
Re:User Agent Changes by bullen on Friday December 13, 2019 @12:30AM (#21779341)
User-Agent should be able to be set by the page following the spec. there is a chromium bug since 2015 that covers it but Google doesn't care:

https://bugs.chromium.org/p/chromium/issues/detail?id=571722

which is blocked by

https://bugs.chromium.org/p/chromium/issues/detail?id=595993

which is blocked by

https://bugs.chromium.org/p/chromium/issues/detail?id=963260

Re:User Agent Changes by Thorrez on Friday December 13, 2019 @01:41AM (#21779609)
Fixing that won't help any of the problems listed in the post.

Also it wouldn't set the User-Agent on top level page loads, just on XHRs/fetches.

Re:User Agent Changes by bullen on Friday December 13, 2019 @10:08AM (#21782201)
True, but it's more important since XHR/Fetch can be used for real-time data!
Re:User Agent Changes by Thorrez on Saturday December 14, 2019 @04:41AM (#21788657)
I don't understand why real-time data is more important than the initial page load.

XHR/Fetch can only read data from the same origin (unless there are CORS headers allowing cross-origin). AIUI, since it's generally the same origin, there generally shouldn't be any User-Agent problems, because the team making the calls is the same team controlling the server-side code. So spoofing a different User-Agent for compatibility shouldn't be necessary.

Re:User Agent Changes by bullen on Saturday December 14, 2019 @01:13PM (#21791026)
Because if you use HTTP for real-time stuff and you make say 10 requests per second and you can't remove the User-Agent header which is like 100+ bytes long that makes for a lot of bytes per month (if you have 1000 users):

"Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"

114x10x60x60x24x30x1000 = 3TB/month

Edit: but now that I checked ingress data is free on all cloud operators! What?