This website requires JavaScript.
Explore
Help
Register
Sign In
rdelaage
/
gmid
Watch
1
Star
0
Fork
0
You've already forked gmid
mirror of
https://github.com/omar-polo/gmid.git
synced
2024-09-29 14:02:00 +02:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
945d22d1f2
gmid
/
.gitignore
8 lines
45 B
Plaintext
Raw
Normal View
History
Unescape
Escape
initial commit
2020-10-02 19:39:00 +02:00
cert.pem
key.pem
TAGS
gmid
implement a valid RFC3986 (URI) parser Up until now I used a "poor man" approach: the uri parser is barely a parser, it tries to extract the path from the request, with some minor checking, and that's all. This obviously is not RFC3986-compliant. The new RFC3986 (URI) parser should be fully compliant. It may accept some invalid URI, but shouldn't reject or mis-parse valid URI. (in particular, the rule for the path is way more relaxed in this parser than it is in the RFC text). A difference with RFC3986 is that we don't even try to parse the (optional) userinfo part of a URI: following the Gemini spec we treat it as an error. A further caveats is that %2F in the path part of the URI is indistinguishable from a literal '/': this is NOT conforming, but due to the scope and use of gmid, I don't see how treat a %2F sequence in the path (reject the URI?).
2020-12-25 13:13:12 +01:00
uri_test
initial commit
2020-10-02 19:39:00 +02:00
*.o
docs
Reference in New Issue
Copy Permalink