Anyway while it's cool to know that the HTTP/2 connection error code exists, I have zero clue on how to make nginx return it (or force it in a situation where it returns it) lol
btw pro-tip if you wanna control the thumbnail of your post: post it without a url first, then edit in the url afterwards. it will not fetch the thumbnail of the url
i do this pro gamer move regularly in red frog site but instead of no url i set the url directly to an image i want to be my post's thumbnail, then edit it to the actual link i want. so you could actually try to rickroll with this technique :P
as i understand it, this mode is never going to happen under normal browsing, though.
I don't think any of my scenarios are normal at all lol :P
HTTP_1_1_REQUIRED (0x0d)
I definitely did not know about this until now, thanks! And searching online it seems like curl does retry its request in HTTP/1.1 if it encounters this. Personally I think it still would've made more sense for the HTTP/2 authors to extend 505 instead, especially since they kept the 1.1 response codes from 2xx-5xx (except 426) anyway, and you can explain to the user why you can't support HTTP/2 for the request in a 505's body... But glad to know there's an error code that can signal to the client to downgrade
nitori wrote
Reply to comment by flabberghaster in Don't you think it's interesting that cheese is the waste product of bacteria eating milk? So in a way if you eat cheese you're eating a germ's shit. by flabberghaster
holy shit