While enabling http/3 on nginx for my personal site, I noticed in the logs most traffic was http/1
-
While enabling http/3 on nginx for my personal site, I noticed in the logs most traffic was http/1.x, and of that almost all was garbage.
So I’ve disabled http/1.x and made exceptions for bots I want and text-based browsers. As expected, my logs are noise free. Now I’m curious to see if there are unintended side effects.
-
While enabling http/3 on nginx for my personal site, I noticed in the logs most traffic was http/1.x, and of that almost all was garbage.
So I’ve disabled http/1.x and made exceptions for bots I want and text-based browsers. As expected, my logs are noise free. Now I’m curious to see if there are unintended side effects.
Looking forward to hearing how this goes...
-
While enabling http/3 on nginx for my personal site, I noticed in the logs most traffic was http/1.x, and of that almost all was garbage.
So I’ve disabled http/1.x and made exceptions for bots I want and text-based browsers. As expected, my logs are noise free. Now I’m curious to see if there are unintended side effects.
-
While enabling http/3 on nginx for my personal site, I noticed in the logs most traffic was http/1.x, and of that almost all was garbage.
So I’ve disabled http/1.x and made exceptions for bots I want and text-based browsers. As expected, my logs are noise free. Now I’m curious to see if there are unintended side effects.
@markmcb That sounds really nice. I would like to know how you did it. Do you have a good source which explains it on how to do it?
-
S skorpy@chaos.social shared this topic