Commits
- Commit:
3c1cf9d07cb679ba444566159538b510902f2de9
- From:
- Omar Polo <op@omarpolo.com>
- Date:
s/uri/iri since we accept IRIs
- Commit:
28778244d67be7024868a5095e5eedda22a3ed98
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix build
- Commit:
85dff1f9c3b18256f0f2cceb802c3c7f2961bc58
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix remote_user for CGI and add -6 flag to enable ipv6
- Commit:
33756bd2353b645a2c046a0807103c309d6d7215
- From:
- Omar Polo <op@omarpolo.com>
- Date:
accept both ipv4 and ipv6
- Commit:
709d6e5ead07ce64dd6625eef05deaedadd8f095
- From:
- Omar Polo <op@omarpolo.com>
- Date:
log also the port of the client
- Commit:
80bbcad5f279e47ec5ccc22076fe1184af7caf5b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
make FATAL and LOG inline functions
other functions that aren't macros anymore. LOG went under a rename
to logs because log is a builtin (the math function), or so gcc says.
- Commit:
9b374f41eee2db5080ef2feb7973228afa3b22aa
- From:
- Omar Polo <op@omarpolo.com>
- Date:
macro reordering
and while there replace SAFE_SETENV with an inline function. LOG is
more difficult to transform into an inline function, given the string
concatenations it does. The other LOG* and FATAL macros are fine as
they already are.
- Commit:
16ace04d459b77fc14ca5b14125ac955769ed72c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
simplify loop
todo was initially there for an optimization: don't loop to MAX_USERS
when you know the upper limit is todo.
- Commit:
4c4167393a95834cdd3af280136c3a0a60752648
- From:
- Omar Polo <op@omarpolo.com>
- Date:
simplify unveil/pledge calls
- Commit:
6c6c7a0ed7de7ec3c4329c6f9892862a4f065451
- From:
- Omar Polo <op@omarpolo.com>
- Date:
rename cgi_setpoll_on_* to cgi_poll_on_*
- Commit:
b3deee7b389408c9c2248fecfd2d1c6bc47e9c97
- From:
- Omar Polo <op@omarpolo.com>
- Date:
initialize error string to avoid returning garbage
- Commit:
4a28dd014ac9a135b84902a0424aed8abbc68cb2
- From:
- Omar Polo <op@omarpolo.com>
- Date:
ignore also SIGHUP
SIGHUP is sent when the tty is detached and by default kills the
process. When we run in the background we don't care anymore about
the tty, so it should be safe for us to ignore SIGHUP. (frankly,
I expected daemon(3) to do stuff like this for us).
- Commit:
5a40216f37fc6b40a0861c685f9903f1a8bbb645
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix CGI with new IRI parser
With new IRI, parser the old assumption of path starting with ./
is no longer valid.
- 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:
488f059ac4c75b8b2e0e610e6445640bce8152e8
- From:
- Omar Polo <op@omarpolo.com>
- Date:
moving declarations to header file