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
th
I'm sorry to make you waste your time with a no Nginx problem.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,282474,283776#msg-283776
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Thu, Apr 04, 2019 at 02:10:16PM -0400, krionz wrote:
Hi there,
> I have been trying to do this without success since December 20, 2018. And i
> still haven't got any answer. Am i missing something on my question? How
> could i improve it ?
Can you show the request you make and the response yo
I have been trying to do this without success since December 20, 2018. And i
still haven't got any answer. Am i missing something on my question? How
could i improve it ?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,282474,283622#msg-283622
__
I'm trying to use wide-open CORS configuration for Nginx. I found this
configuration: https://enable-cors.org/server_nginx.html. Since i started to
use this configuration Nginx only serves an empty response with 200 status
code. I'm using Nginx with PHP-FPM. I have already checked and there is
noth
