mapzen / apiaxle Goto Github PK

keyless keys currently live forever, and the usage limits are set when the ip is first used, so if keyless limits change for an api, we need to either delete or update the keyless keys associated with it.

we could add code to apiaxle that updates or clears an api's keyless keys when the api's keyless limits are changed.

https://github.com/missinglink/apiaxle/tree/duplicate_cors_headers

@missinglink mind talking me through how to test this?

The vector tiles appear to be returning 429 errors.
http://themapisnot.com/issue-iv-patricio-gonzalez-vivo-jen-lowe#canvas

Here is the API key, which maybe doesn't have so many requests to trip the free tier limit?
https://mapzen.com/admin/keys/mapzen-YoRQaZF?selected=Requests%2CMonth&shown=

https://github.com/mapzen/apiaxle/blob/integration/proxy/apiaxle-proxy.coffee#L113-L119

for example if the header looks like this:
X-Forwarded-For: 108.176.27.194, 199.27.76.25
we should use the first one