Closed boesing closed 7 years ago
Well, just setting the status code to 204
wont fix that issue.
Might be a problem with the NGINX configuration.
Going to give more feedback here if we got a fix for this.
Just a sidenote: I guess 204 would be the correct response code either and I guess that any browser can interpret this. However, the fix was to update NGINX at all since there were some fixes in newer versions to handle empty responses from upstreams.
Hey guys,
we've got problems with nginx 1.6.2 and the preflight response. We are getting the following error quite often:
The response is being redirected to upstream either, but the logs are being flooded. I currently created a workaround with another Listener which checks for preflight request and changes the response status code but I would prefer if there might be no extra listener which manipulates the status code tho.
I've created a PR #41 which will set
204
by default.