Commits
- Commit:
12042ad7003375b746b4e2bccbf33ae7a90cbb98
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add a configure script and some compat
tested on openbsd, alpine and void
- Commit:
15902770073dd67df3a9af0f6da7d63bfb031d72
- From:
- Omar Polo <op@omarpolo.com>
- Date:
conf & vhosts
* gmid.c (main): changed behaviour: daemon off by default
(main): changed -c in -C (cert option)
(main): changed -k in -K (key option, for consistency with -C)
(main): added -c to load a configuration
(main): certs, key and doc (-C -K and -d) doesn't have a default value anymore
(handle_handshake): add vhosts support
- Commit:
3c1cf9d07cb679ba444566159538b510902f2de9
- From:
- Omar Polo <op@omarpolo.com>
- Date:
s/uri/iri since we accept IRIs
- Commit:
33d32d1fd66a577f22f3f33f238e8dac44ec9995
- From:
- Omar Polo <op@omarpolo.com>
- Date:
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?).
- Commit:
3e4749f7f9b6c37c1870ed3c0561083de17f2197
- From:
- Omar Polo <op@omarpolo.com>
- Date:
initial commit