Yes. It does.
Here’s the last 5 lines of the access.log file before attempting to register the event:
ubuntu@twitchevt:~$ sudo tail -n 3 /var/log/nginx/access.log
157.245.176.143 - - [03/Jan/2022:15:06:42 +0000] "SSTP_DUPLEX_POST /sra_{BA195980-CD49-458b-9E23-C84EE0ADCD75}/ HTTP/1.1" 400 166 "-" "-"
45.146.165.37 - - [03/Jan/2022:15:40:17 +0000] "GET /console/ HTTP/1.1" 200 5 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36"
216.252.208.243 - - [03/Jan/2022:15:49:14 +0000] "POST / HTTP/1.1" 200 36 "-" "twitch-cli/1.1.5"
And immediately after trying to register the event:
ubuntu@twitchevt:~$ sudo tail -n 3 /var/log/nginx/access.log
45.146.165.37 - - [03/Jan/2022:15:40:17 +0000] "GET /console/ HTTP/1.1" 200 5 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36"
216.252.208.243 - - [03/Jan/2022:15:49:14 +0000] "POST / HTTP/1.1" 200 36 "-" "twitch-cli/1.1.5"
52.12.79.235 - - [03/Jan/2022:15:50:07 +0000] "POST / HTTP/1.1" 200 36 "-" "Go-http-client/1.1"
I am no longer using Cloudflare because the Twitch API is not capable of handling an HTTP response if UTF-8 encoding is specified. Cloudflare does not, so far as I can tell, have a way to disable the UTF-8 encoding from being added, so it’s not compatible with Twitch.
Anything nginx receives is passed to my script via a proxy_pass call. My script just doesn’t log anything—it doesn’t write received requests to a log file because nginx is already doing that.
I only meant my script doesn’t log the requests. It is absolutely receiving them.