dataservices-api/server
Mario de Frutos 33f40bc945 TOMTOM uses 403 instead of 429 for rate limiting
That has a great problem when we're dealing with legit 403 status for
example deactivated user, forbidden access, etc.

I've added a check for the HTTP header `X-Error-Detail-Header` in order
to distinguish between legit 403 and 429 error messages

Possible values for `X-Error-Detail-Header` in a 403 error:

  o Service Requires SSL : http is used instead of https (secure)

  o Invalid Referer : invalid 'Referer' header value is send
  to https://api.tomtom.com and allowed referer values are
  configured on specific API key

  o Account Over Queries Per Second Limit : rate limit exceeded

  o Account Inactive : incorrect API key/API key no longer valid
2018-10-31 12:59:13 +01:00
..
extension Server changes 2018-09-11 14:35:02 +02:00
lib TOMTOM uses 403 instead of 429 for rate limiting 2018-10-31 12:59:13 +01:00
__init__.py Bulk geocoding refactor 2018-06-29 14:59:07 +02:00