-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GG: /.. reported as invalid IRI #12
Comments
good catch, I haven't thought about that case.
I had in mind to improve the IRI handling and separate the parsing and cleanup phases, now I have a strong reason to do that :) |
If you don't mind, I'd keep this open. While it's not a top-priority, I still like to to eventually fix it ^^" |
No problem! just went through my old stuff and removed the inactive-seeming ones |
Took a while to fix this, oops :) When I wrote the parser I was a bit paranoic and decided to reject altogether paths that tried to "escape" the root. However, RFC 3986 § 5.2.4 in the algorithm "remove_dot_segments" explicitly allows for it. |
Requesting the address
gemini://localhost/../
returns the errorgg: invalid IRI: illegal path
, even though it should be a valid IRIgemini://localhost/./...../
(arbitrarily many.
at the end) works, and will return the index of localhost, if requested on a gmid serverThe text was updated successfully, but these errors were encountered: