Tree
- Tree:
9184f10e29ac2182f518831796829a7470ad7fc2
- Date:
- Message:
- trim initial forward slashes this parse gemini://example.com///foo into an IRI whose path is "foo". I'm not 100% this is standard-compliant but: 1. it seems a logical consequence of the URI/IRI cleaning algo (where we drop sequential slashes) 2. practically speaking serving file a sequence of forward slashes doesn't really make sense, even in the case of CGI scripts