Context Navigation

Changes between Version 3 and Version 4 of Ticket #63316, comment 27

-              v3
+              v4
 As I say, leaving the empty host dangling through the function is not doing any good. Also, we can try to handle that `:///` (or `://:port/`) somewhere in the middle of `redirect_canonical`.
+I would simply short-circuit, as I said. An Empty host can't be done with HTTP1.1+ and supporting HTTP1.0 doesn't make much sense in 2025.
+In case we want to leave this as I proposed in my first patch.
+I would simply short-circuit, as I said. An Empty host can't be done with HTTP1.1+ and supporting HTTP1.0 doesn't make much sense in 2025, but still a "catch-all" `in user_home` could also make sense, though.
 But if we are willing to let it go through, I'm still trying to figure out how to trigger this with a Unit Test.