Hi @jamesevans I think you should allow more time particularly for devs using the unified api in their apps. Apps users are slow to update specially on Android and I can foresee bad ratings coming from users whose app suddenly stopped working. So please consider at least a couple of months or three for this kind of critical changes. Thank you.
@nakkore We would love to give a longer lead time but there is some urgency to get this change in place. I’ve contacted all the main transport apps that use our data and they are happy with the timeframe we’ve given them. Apologies to anyone else who is inconvenienced. We try our hardest to avoid changes that could break third party apps as we know our customers rely on them but in this instance we had no choice.
As long as it’s populated, you should be OK. Sometimes we block particular user agents if there’s malicious or suspicious activity associated with it, but that’s quite rare.
Thanks. If there is no default User-Agent created by PHP, then I guess I’m going to have to contact MTR Crossrail and tell them their customer app is going to stop working…
Agree, that ought to be done. I’m assuming firefox (desktop and android) will send a user agent unless I’ve told it not to, but I’m not sure how I would test it in both cases. A test server would confirm it properly.
I’m working on setting up a test domain for this. It’s proving tricky as it’s a global firewall setting for all our outward-facing web applications. I’ll let you know how I get on.
@briantist - curl on the command line does seem to send a user agent in the headers. You can see this by using curl -v
> GET /Line/85/Route HTTP/2
> Host: api.tfl.gov.uk
> User-Agent: curl/7.54.0