Invalid URL error when domain contains multiple slashes at the end

[screenfluent]

Astro Info

Astro                    v5.0.5
Node                     v18.20.3
System                   Linux (x64)
Package Manager          unknown
Output                   static
Adapter                  none
Integrations             none

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

Astro throws 500 Internal Server Error with "Invalid URL" when main domain contains double or more slashes at the end. This happens in development server, production build, StackBlitz. This is not a browser issue. The problem occurs at server level and can be reproduced with curl.

What's the expected result?

• Redirect to normalized version

Instead the server crashes with 500 error.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-726xsb6l-xoqxvvkc

Participation

• I am willing to submit a pull request for this issue.

[ascorbic]

I can only reproduce this in one scenario: when running astro dev, and requesting http://localhost:1234//. I can see the place where this is failing. I can't reproduce it for other scenarios though: it works if there's anything else in the path (e.g. http://localhost:1234/something//) and I can't reproduce it in a production build. Do you have reproductions for the other cases?

[screenfluent]

I discovered it when deployed to Cloudflare Pages and accidentally put two // at the end and to my surprise, the page loaded keeping them. So I added more and they stayed too. I spent quite a good amount of time fighting with CF deployment and ultimately did localhost testing to see the invalid URL error.

I would love to see Astro paying attention to slashes, as someone who built their first website in 1998 and cut their teeth on SEO. I know that to this day (crazy!) Google can't resolve the issue with slashes at the end of URLs and they're treated as two different competing addresses that harm SEO. And users link in various surprising and often incorrect ways.

[ascorbic]

So to be clear, there are two issues? Locally, there's the invalid URL problem, and on Cloudflare it's that multiple slashes are ignored and treated the same as a single slash?

[screenfluent]

Hmmm I'm not sure if it's one issue that behaves differently depending on the environment or two separate ones. I'll deploy basic clean version to CF again to see if the behavior is the same.

[ascorbic]

The code with the invalid URL is in the dev server code, so if it also happens elsewhere then it's two issues.