Remaining credits for 'CORS' requests not accessible about directions-api

[karussell]

This will be fixed in the next days via adding the header:
Access-Control-Expose-Headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-RateLimit-Credits

[opoto]

Hi
Had this fix been released?
Thanks

[karussell]

Hmmh, it should have been but does not look so. Will investigate.

[karussell]

We set Access-Control-Expose-Headers only if the http method is "options", which should make it working on all recent browsers. If you had a problem with this, would you mind to let me know your browser version etc?

[opoto]

Tested on latest Chrome and Mozilla on Windows, Ubuntu and Android and it does not work.
Why only set the header on OPTIONS? It should be on GET too.
Whether it works or not can be easily tested with one click (replace MY-KEY with valid key):
http://www.test-cors.org/#?client_method=GET&client_credentials=false&server_url=https%3A%2F%2Fgraphhopper.com%2Fapi%2F1%2Froute%3Fpoint%3D43.2301414%2C5.4369798%26point%3D43.23088361474902%2C5.43874740600586%26point%3D43.23150897353908%2C5.442867279052735%26point%3D43.23113375903503%2C5.444755554199219%26instructions%3Dtrue%26type%3Djson%26key%3DMY-KEY%26vehicle%3Dfoot&server_enable=true&server_status=200&server_credentials=false&server_tabs=remote

[karussell]

Strange, a customer requested this and tested this with the same website and it worked for them. Will have to read more what the correct procedure would be.

[karussell]

Sorry, was confusing Access-Control-Allow-Headers (only for preflight query) and Access-Control-Expose-Headers. Will fix

[karussell]

Fixed