Conversation

Notices

1. :mima_rule: Mima-sama (mima@makai.chaotic.ninja)'s status on Monday, 19-Aug-2024 22:37:06 JST :mima_rule: Mima-sama

   Don't you just like it when web #archiving sites encounter an #HTTP 505 when using #HTTP2 and not be smart about it like trying again with HTTP/1 :seija_coffee:
   
   Tbf the spec doesn't say anything about what clients should do when they encounter 505, so I'm blaming the HTTP/2 (and HTTP/3!) spec writers for not extending that status code to allow fallback (which is an encouraged behavior!)
   
   https://archive.md/FGU7F
   https://ghostarchive.org/archive/lw8if

   • Izuru Yakumo (八雲 出流) (yakumo_izuru@misskey.m544.net)'s status on Monday, 19-Aug-2024 22:37:05 JST Izuru Yakumo (八雲 出流)

     in reply to

     @mima@makai.chaotic.ninja there isn't a 'Downgrade' header anyways

   • :mima_rule: Mima-sama (mima@makai.chaotic.ninja)'s status on Monday, 19-Aug-2024 22:37:06 JST :mima_rule: Mima-sama

     in reply to

     Also if you're thinking of being clever and have the server respond with a 426 with Upgrade: HTTP/1.1, that won't work because HTTP/2 has removed support for the Upgrade header
     
     https://httpwg.org/specs/rfc9113.html#informational-responses