CORS- proxy needed?

I spotted this in the bolt.new github issues. Any chance this feature will be ported soon to bolt.diy? I feel like this would solve a ton of these CORS issues like for example, this one: Importing from Bolt.new - COEP and CORS policy management - #12 by shawn

From here: Can't connect to external service (CORS issues) · Issue #3164 · stackblitz/bolt.new · GitHub

2 Likes

Hi @rachelslurs,

thanks for the input. I moved your topic to [bolt.diy] New Features Discussion.

The roadmap / features for the next months will be discussed in the next week.

@ColeMedin fyi

2 Likes

Yep i ended up in a deadend of cors issues with stripe, gave up and added paypal buttons instead.

1 Like

I assume since it’s been rolled out in Bolt.new, it should be a relatively easy feature to duplicate. It’s not like it hasn’t been done before and it’s one of the biggest issues I’ve faced and it’s stopped me in my tracks on 3 apps. All CORS or COEP policies or Geolocation blocked because of the development environment limitations.

Please may I ask that it be prioritised.

We merged cors proxy for github

Its currently used for github feature but its generic cors proxy so can be used for this

It will just require some implementation for AI to understand when and how to route requests trough it

4 Likes

@wonderwhy.er I think you can just let program a OpenStreetMap application, then you should get some errors:

3 Likes

Can I ask if you think this will be the same solution that exposes the environment so that Location services can also be served without adding additional code that’s redundant once deployed to the real world?
@leex279 - honk honk…!

Ok, so its not about cors proxy.

Thanks @leex279 for your leaflet example.
I tested it in bolt.new and there it worked
Explored what are differences and found how to fix
Here is PR where its working

2 Likes

Nice work @wonderwhy.er!

1 Like

See: Importing from Bolt.new - COEP and CORS policy management - #22 by leex279

Closed