News for hackers. Stuff that matters.
Re:User Agent Changes by toast0 on Thursday December 12, 2019 @09:12PM (#21778585)
User-Agent for browsers is pretty much useless now, but it's still a pretty useful name for a header if you want to put real information in it. Ex, if you're calling an api, it's nice to have a version number and a name/contact so broken things can be fixed.

I don't remember if HTTP/2 (and presumably /3) has a initial dictionary for header compression, they could have a suggested value in there, so if you want to look like a browser, you can use that at a low byte cost.

Re:User Agent Changes by edoceo on Thursday December 12, 2019 @09:27PM (#21778664)
I make an API, for narrow use case. All calls have to be from a registered UA, among other things forms the HMAC sig.
Re:User Agent Changes by sk5t on Thursday December 12, 2019 @09:44PM (#21778730)
You have created a perverse-sounding design.
Re:User Agent Changes by neikos on Friday December 13, 2019 @02:32AM (#21779790)
This sounds like authentication with extra steps? Why not just send a bearer token?
Re:User Agent Changes by edoceo on Friday December 13, 2019 @08:00AM (#21781141)
We do. Header is for message signing. And UA has to be registered, part of the spec provided by client.