Datasette server redirects //example.com/ to https://example.com

[psd]

The datasette server command 302 redirects paths such as //example.com/ to '//example.com' which is followed by curl and browsers to 'https://example.com'.

Note, the path needs to begin with double-slash and end in a slash.

There's a log of how to reproduce the issue locally in this gist.

I've been unable to reproduce this issue on production servers, so could be something to flag more strongly in documentation if this is expected behaviour in development.