Yeah I would say that falls under the origin defining both paths as equivalent.
> Therefore, collapsing // to / in HTTP URL path segments is not correct normalization. It produces a different, non-equivalent identifier unless the origin explicitly defines those two paths as equivalent.
Brain fart. I mean CDU. I guess they behave like Greens so much I got them confused. Also, not "sacked" but not renewed, but it's kind of the same thing in practice.
So till november 2026 or so everything is fine. Then I will probably have to switch to Linux.
reply