Commits
- Commit:
12042ad7003375b746b4e2bccbf33ae7a90cbb98
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add a configure script and some compat
tested on openbsd, alpine and void
- Commit:
5bc29bc915c1929d8cf9d7a29f225087029efe6a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
remove README.md target
leftover from when README.md was generated by gmid.1
- Commit:
0fbe79b33c1d16b0611851e2019558ce8888a02e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
improve mime handling
we still have an hardcoded list, but this implements the API needed to
modify the mappings.
- Commit:
d3a08f4d172687d4e3e60e7faaa8830bb7f9f9db
- From:
- Omar Polo <op@omarpolo.com>
- Date:
reorganize: move bunch of functions to server.c
cgi.c wasn't really needed; it better to group all the server related
functions together, cgi or not. Now gmid.c contains only startup and
utility code.
- Commit:
771d8f281baa6f15913d705365e00c3128feac8b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
build docs + install and static targets
- Commit:
364f10dbcd3b053730a4ad47042e0d8222aada47
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add runtime tests for the server
- Commit:
881a9dd9c2aebbf73f333dd3d8be4ce5400f717f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
split into two processes: listener and executor
this way, we can sandbox the listener with seccomp (todo) or capsicum
(already done) and still have CGI scripts. When we want to exec, we
tell the executor what to do, the executor executes the scripts and
send the fd backt to the listener.
- Commit:
7edc455ab4ba2c408558876339ac77a3104d0de2
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move cgi stuff to its own file
- Commit:
dafb57b8af432d800219a8e17900e1ac56a65c14
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sandbox also on FreeBSD with capsicum
- 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:
b9220ca4de556f24be9cdc0d478109b75cd476ae
- From:
- Omar Polo <op@omarpolo.com>
- Date:
new README + wording in manpage
- Commit:
ef04b55160759b22db67f14c703a4343c4741e8b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
switch to Bjoern Hoehrmann UTF-8 decoder
It's correct, while my hacked valid_multibyte_utf8 would allow things
that aren't technically UTF8.
- 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:
10fed44c7988d70a4dc2f57e24ca92b3f72924b8
- From:
- Omar Polo <op@omarpolo.com>
- Date:
improve make error message if etags is not found
the ‘|| true’ idiom leads to better make error. Now the ‘-’ becomes a
bit redundant tho…