Welcome! Log In Create A New Profile

Advanced

Re: Only receiving an empty response with 200 status code when using CORS on Nginx 1.14

April 14, 2019 11:36AM
The problem actually was with my understanding of the CORS policy. When i make a PATCH the browser makes an OPTIONS to check if i can use the PATCH method, and even if i answer this OPTIONS request saying that i accept the PATCH method, when i receive the actual PATCH request i must again answer this request saying that i allow the PATCH request, otherwise the browser will not allow me to use the answer given by my server.
Subject Author Posted

Only receiving an empty response with 200 status code when using CORS on Nginx 1.14

krionz December 26, 2018 05:40AM

Re: Only receiving an empty response with 200 status code when using CORS on Nginx 1.14

krionz April 04, 2019 02:10PM

Re: Only receiving an empty response with 200 status code when using CORS on Nginx 1.14

Francis Daly April 04, 2019 07:18PM

Re: Only receiving an empty response with 200 status code when using CORS on Nginx 1.14

krionz April 14, 2019 11:36AM

Re: Only receiving an empty response with 200 status code when using CORS on Nginx 1.14

krionz April 14, 2019 11:37AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 316
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready