Since open elevation is an open API I think that it would be logic to add the <code cl

Agree, when calling the api from code (java) I am getting: Failed to load <a

Add the Access-Control-Allow-Origin:* in the header response about open-elevation HOT 6 CLOSED

gregoryalary commented on July 21, 2024 2

Add the Access-Control-Allow-Origin:* in the header response

from open-elevation.

Comments (6)

Jorl17 commented on July 21, 2024 2

Hi, thank you for your feedback :)

Support has been added for CORS. It's obvious it should have been added from the very start.

Cheers!

from open-elevation.

mark-sts commented on July 21, 2024 1

Agree, when calling the api from code (javascript) I am getting:
Failed to load https://api.open-elevation.com/api/v1/lookup?locations=10%2C10: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.

Works fine when called live from the browser url

from open-elevation.

Rcalaf commented on July 21, 2024

Hi,

We experience the same issue, not sure if you have updated the server or added som patch but again when calling the API through JS receiving a CORS error.

Thanks for checking,

from open-elevation.

Jorl17 commented on July 21, 2024

Hi.

Our service has recently reached a bottleneck once more. Some developers are using it carelessly and, since we don't enforce API keys or similar measures -- and are low on donations -- the servers are blowing up. In particular, I can tell you that the app "Ski Tracker" uses our services and is completely bombarding us with requests non-stop. This made the service unusable for most other users.

As a measure to try to workaround Ski Tracker's aggressive usage of our service (we're being bombarded with hundreds of requests per second), we implemented a more thorough rate limiting system. Sadly, I believe this system is leading to your problems. I have just done some adjustments that might improve your situation. Please tell me if the situation has improved or not.

Sorry for the inconvenience. It's not easy to maintain a free service :(

EDIT: I have noticed that in your logs you received a 504. This is just a general timeout and failure. It may fail due to CORS but it isn't actually a CORS problem, just a problem with the server being overloaded. Sadly, no amount of rate limiting is going to fix this issue (only a beefier machine will help, sadly)

from open-elevation.

Rcalaf commented on July 21, 2024

…

On 1 Feb 2022, at 18:57, João Ricardo Lourenço ***@***.***> wrote: Hi. Our service has recently reached a bottleneck once more. Some developers are using it carelessly and, since we don't enforce API keys or similar measures -- and are low on donations -- the servers are blowing up. In particular, I can tell you that the app "Ski Tracker" uses our services and is completely bombarding us with requests non-stop. This made the service unusable for most other users. As a measure to try to workaround Ski Tracker's aggressive usage of our service (we're being bombarded with hundreds of requests per second), we implemented more a thorough rate limiting system. Sadly, I believe this system is leading to your problems. I have just done some adjustments that might improve your situation. Please tell me if the situation has improved or not. Sorry for the inconvenience. It's not easy to maintain a free service :( — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.

from open-elevation.

Rcalaf commented on July 21, 2024

Good morning João, We finally have deployed our own elevation server, so we won't be bothering yours :) Thank you for your help and your open-source service! RCC El mar, 1 feb 2022 a las 22:12, Roger Calaf ***@***.***>) escribió:

…

Hi! Thank you very much for your response, totally comprensible. We will try to implement our own server so we don’t kill yours ;) We really appreciate your effort trying to help us and improve the service so quickly. Kind regards Roger Calaf Creative Technologist Portfolio: rogercalaf.com Twitter: @roger_calaf On 1 Feb 2022, at 18:57, João Ricardo Lourenço ***@***.***> wrote: Hi. Our service has recently reached a bottleneck once more. Some developers are using it carelessly and, since we don't enforce API keys or similar measures -- and are low on donations -- the servers are blowing up. In particular, I can tell you that the app "Ski Tracker" uses our services and is completely bombarding us with requests non-stop. This made the service unusable for most other users. As a measure to try to workaround Ski Tracker's aggressive usage of our service (we're being bombarded with hundreds of requests per second), we implemented more a thorough rate limiting system. Sadly, I believe this system is leading to your problems. I have just done some adjustments that might improve your situation. Please tell me if the situation has improved or not. Sorry for the inconvenience. It's not easy to maintain a free service :( — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAS4LNOLWQ36OUEVAPFDHDTUZANHFANCNFSM4EAYHMVA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

-- Roger Calaf Creative Technologist Portofolio: rogercalaf.com LinkedIn: www.linkedin.com/in/roger-calaf-5068378 Skype: rcalaf.cot *Este correo electrónico y sus archivos adjuntos son propiedad privilegiada y confidencial. Ya que sirven exclusivamente para el destinatario (s) nombrado. Si recibe este correo por error, por favor notifique al remitente inmediatamente. Usted no puede revelar su contenido a ninguna otra persona, utilizar la información contenida en ella para cualquier fin, almacenar o copiar sin el permiso explícito del remitente. No se puede garantizar que sean confidenciales las comunicaciones por Internet, ni que sean seguras o libres de errores dado que pueden ser interceptados, manipulados, llegar tarde o contener virus. El remitente, por lo tanto no se hace responsable de los errores u omisiones en el contexto de este mensaje, que surgen como consecuencia de la transmisión de Internet.* *This e-mail and any attachments are the privileged and confidential property. They are intended solely for the named recipient(s). If you receive this e-mail in error, please notify the sender immediately. You may not disclose the contents to any other person, use information contained in it for any purpose, store or copy it without the explicit permission of the sender. Internet communications cannot be guaranteed to be confidential, secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The sender therefore does not accept liability for any errors or omissions in the context of this message which arise as a result of Internet transmission.*

from open-elevation.

Add the Access-Control-Allow-Origin:* in the header response about open-elevation HOT 6 CLOSED

Comments (6)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent