>>>>> Jeffrey Walton <noloa...@gmail.com>:
> The first two which succeed have a user agent string ("Expanse..." and
> "Mozilla/5.0..."). The third one which fails lacks the user agent
> string ("-").
> I'm not sure if that makes the difference in the behavior you are observing.
> You may be able to test it with cURL or Wget. Here's how to fiddle
> with the user agent with cURL:
> <https://everything.curl.dev/http/modify/user-agent.html>; and Wget:
> <https://www.gnu.org/software/wget/manual/wget.html#user_agent>.
Hm... everything I try gets 444...?
sb@marquez:~$ curl http://<server's IPv4 address>/
curl: (52) Empty reply from server
sb@marquez:~$ curl https://<server's IPv4 address>/
curl: (60) SSL: no alternative certificate subject name matches target host
name '<server's IPv4 address>'
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
sb@marquez:~$ curl http://<server's IPv4 address>/ --user-agent 'Mozilla/5.0
(Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrom324.190 Safari/537.36'
curl: (52) Empty reply from server
sb@marquez:~$
(As expected only HTTP on port 80 will work at all for the IP address,
since there is no certificate matchinng the IP number as hostname)
_______________________________________________
nginx mailing list
nginx@nginx.org
https://mailman.nginx.org/mailman/listinfo/nginx
