Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

I've been searching and looking everywhere on the internet and on these forms for days to help understand this issue and how to properly setup NGINX Ingress with Wordpress-fpm. I'm rather new to Kubernetes and all so I've been working on setting this up to help me learn it all.

I can get it to work using the image of Wordpress that has Apache included (Wordpress:latest) but I rather use NG

So far we don't enable the SNI extension when communicating with upstream. If upstream server depends on SNI to select proper certificate, then the TLS/SSL handshaking will fail. So we should carry the SNI extension.

Nginx has a directive named proxy_ssl_server_name.

Syntax: proxy_ssl_server_name on | off;
proxy_ssl_server_name 

Since maxmind no longer provides the legacy GeoIP databases could it might be possible to update the nxtool to use GeoIP2?

In lieu of #283, implement Stackdriver Canary Analysis for use in GKE.

Percona is quite strict on having primary keys on all tables (and rightly so).
Please add primary keys to all tables, even if it's just an auto-increment.

It's mostly just the following tables:
authentication_logs (could just get a auto-increment primary key added)
identity_verification_tokens (could just set the token as primary key)