All topics

API Call Method being passed as "options"

Funktionalized

2 months ago
I have a post request that is using the cloudflare proxy to make a request to a fastapi endpoint. When the proxy sends the request for some reason it is using a method called "options" and it is causing a 405 method not allowed error.

I have the API Call setup as a post request in toddle.
filename.plain; charset=utf-8
Tod

2 months ago
Great energy @Funktionalized! Your continuous contribution to the toddle Community just made you advance to Community Level 3!
Erik Beuschau

2 months ago
The OPTIONS method is usually used for cross origin requests (CORS). So since your app is on a different origin (domain) than the back-end, it will first send an OPTIONS request to verify that it's allowed to perform that operation.
In your case, it seems your endpoint is not open for CORS.
Perhaps you could try enabling the proxy checkbox at the bottom of the API dialog to see if that helps? 🤞
@Erik Beuschau
The OPTIONS method is usually used for cross origin requests (CORS). So since your app is on a different origin (domain) than the back-end, it will first send an OPTIONS request to verify that it's allowed to perform that operation.
In your case, it seems your endpoint is not open for CORS.
Perhaps you could try enabling the proxy checkbox at the bottom of the API dialog to see if that helps? 🤞
Funktionalized

2 months ago
hmm weird ive updated my middleware rules, and it works when i try it using auto fetch. But not when im testing my app.
Andreas Møller

2 months ago
Are you sure proxy is turned on?
This sounds like a pre-flight request.
@Andreas Møller
Are you sure proxy is turned on?
This sounds like a pre-flight request.
Funktionalized

2 months ago
Yeah it was fixed, im just gonna assume it was an issue the query parameter. rather than sending long text as a payload. Idk its working now though.
Andreas Møller

2 months ago
When the proxy is turned off you are making what called a cross origin resouce request: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
There are some security issues related to that, so the browser will often make what is called a pre-flight request to check if the server allows these kinds of requests.
Pre-flight requests are an OPTION request (and one of the only times OPTION requests are used)
When you turn the proxy on the request goes through our gateway first, and you dont have to do the preflight request.
Lucas G

2 months ago
Everyone loves dealing with CORS!
Andreas Møller

2 months ago
That was the original reason for the proxy. Auth was just kind of an obvious next step

API Call Method being passed as "options"

Funktionalized

Tod

Erik Beuschau

Funktionalized

Andreas Møller

Funktionalized

Andreas Møller

Lucas G

Andreas Møller

Stop scrolling. Start building.

Chat with @team-toddle

Video call our CEO

Get in touch!

Product

Company

Resources

Community