Yes he solution is in my post. You need to fix your gateway because it should not add the header twice. Curl is not affected because it is not a web browser
> On Aug 4, 2016, at 1:49 PM, Abhishek Goswami <[email protected]> wrote: > > [...] >> On Tuesday, 2 August 2016 12:36:17 UTC+5:30, tony tam wrote: >> That's just how CORS works. When you post a body it must do a preflight >> check via options. Posting with www-form-urlencoded will not > [/...] > So can you please tell me as to how can i solve it because when i run the > curl command which is generated by itself, provides me correct output but > through swagger console it shows "no content" and in network tab it shows > "404" that means either server is returning 404 when it's requested through > swagger or my code is wrong. If server setting is required then please guide > me because i have already made some changes on server to enable request from > swagger but when i am passing body parameter, it doesn't work. If my code is > wrong then what are the possible errors/points to look at? > Thanks in advance > -- > You received this message because you are subscribed to the Google Groups > "Swagger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
