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

1 files changed, 4 insertions, 0 deletions

diff --git a/iri.c b/iri.c
index 26ee920..beba368 100644
--- a/iri.c
+++ b/iri.c
@@ -293,6 +293,10 @@ parse_path(struct parser *p)
 {
 	char c;
 
+	/* trim initial slashes */
+	while (*p->iri == '/')
+		p->iri++;
+
 	p->parsed->path = p->iri;
 	if (*p->iri == '\0') {
 		p->parsed->query = p->parsed->fragment = p->iri;