Lyft API近期出现CORS错误：ETA及费用估算端点跨域问题咨询

Hey, you’re not alone in dealing with this — I’ve noticed several other developers bringing up the exact same problem in dev communities lately.

Here’s what we’ve pieced together so far:

• The Core Problem: The ETA (driver estimated arrival time) and cost estimation endpoints have stopped returning the access-control-allow-origin:* response header. This directly triggers CORS blocks when trying to fetch data directly from browsers, forcing many of us to route requests through our own backend servers as a workaround. As you pointed out, this proxy step feels totally unnecessary and adds extra overhead.
• Policy Shift or Bug?: Right now, there’s no official communication from Lyft stating this is a deliberate policy change. A number of developers suspect it’s an unintended regression from a recent API update, since other Lyft endpoints still include the required CORS headers. Lyft’s developer support has been slow to address inquiries about this, so we’re still waiting on clarity here.
• Documentation Check: I’ve reviewed the Lyft reference docs for the availability/driver ETA endpoint, and there’s no note of any recent CORS policy adjustments listed there. It’s a good idea to monitor Lyft’s developer channels for any updates that might explain this change.

内容的提问来源于stack exchange，提问作者egrubbs