-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gisgraphy tests fail due to missing key #48
Comments
I suggest using the demo server https://services.gisgraphy.com/ |
It would still fail:
|
I suggest that you put a user-agent that I accept on server side on the demo server, as I have done on this PR : DenisCarriere/geocoder@a0248e3 what about 'geocoder-converter' |
Ok |
Please add a user agent only for tests (something like a variable only feed in tests) I don t want to white list all the users of the geocoder converter 😊 |
Wouldn't it be easier to create a very limited key for this purpose? Changing the user-agent is a possible solution, but since we make this transparent, every user could just switch to the geocoding-converter user agent as well. Anyway changing the user agent just for tests seems to be not straight forward. We could add a config variable to change the user-agent (maybe we do this globally for all providers or only gisgraphy). Then we would set |
That 's I got in mind too :-). Just put a user-agent different for the tests. what about 'geocoder-converter' for the "main software" and 'geocoder-converter' for tests? |
We could put our API key for gisgraphy in the hidden section here at github, but highly likely it will be exposed in the logging. Or should we temporary disable gisgraphy tests for travis?
The text was updated successfully, but these errors were encountered: