DELETE not working? about flask-cors

Ok, I got what i was doing wrong now, if you look at the link i've provided above, the route which is tagged for DELETE requests actually has a duplicated route with same rule but different method (which is POST), and on that POST route I forgot to delete the @cross_origin decorator which allows only POST methods (I have those because before i upgraded to v1.7, i was using v1.3), and when i deleted it, it started to work like a charm now.

[corydolphin]

Hey Charles,

I'm glad you were able to figure things out!

1. Is there any feedback you have on the documentation so future users do
   not run into this issue? I am planning to add logging of the CORS options
   on a per request basis, perhaps this would've helped the situation to make
   it clear that there was both app-level and decorator configuration
   occurring.
2. I will make sure we support all HTTP verbs, including PATCH/DELETE/PUT.

Thanks for reporting the issue and double points for resolving and posting
the solution!

On Monday, August 18, 2014, Charles Jordan Cabero [email protected]
wrote:

Ok, I got what i was doing wrong now, if you look at the link i've
provided above, the route which is tagged for DELETE requests actually has
a duplicated route with same rule but different method (which is POST), and
on that POST route I forgot to delete the @cross_origin decorator which
allows only POST methods (I have those because before i upgraded to v1.7, i
was using v1.3), and when i deleted it, it started to work like a charm now.

—
Reply to this email directly or view it on GitHub
#55 (comment).

Sent from my mobile, please excuse spelling and brevity

[adamelmohamad]

life saver