Commits
- 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
- Commit:
51d876f030b17e23ac08b729f2b20fb72653bc0a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
always check absolutify_path return
- Commit:
231bfcdc0391cde9077e6ae0cd14dc6831fb1b88
- From:
- Omar Polo <op@omarpolo.com>
- Date:
make -d handle correctly non-absolute paths
before the -d option only accepted absolute paths, and this wasn't
documented. Even more, with the default value of "docs" it won't
work. Now it transforms all relative paths to absolute paths before
going on.
- Commit:
dd3e110a707fc9ac5653969b22e6489f7e100d50
- From:
- Omar Polo <op@omarpolo.com>
- Date:
reorder & fmt
- Commit:
d7802bb44a8562917b58bfc76f135ddf4fcbbe3b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
logging reworked and daemonize by default
The -l option was removed: now it logs on syslog if -f (foreground) is
not passed.
- Commit:
677afbd3f873425bcc6f9a23be7efe3066aed70a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
clients certs support for CGI
internally, gmid doesn’t care if the client issued a certificate, but
now we pass that information to the CGI script in some new environment
variables.
- Commit:
c603f1260de9fb2cc81dd886a5ddb8e43caa9d0c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix bug introduced in last version regarding full URLs
gemini://example.com was incorrectly parsed.
- Commit:
7cd6880b84f3bba0cc8b11ef452dba18e0b51155
- From:
- Omar Polo <op@omarpolo.com>
- Date:
correctly handle also non absolute URLs
- Commit:
ae2ad03ec0ae5f2300472239eb48f3e23d467fe2
- From:
- Omar Polo <op@omarpolo.com>
- Date:
handle //example.com urls
- Commit:
721e2325296b1556eb0d2224ef37b387091dff43
- From:
- Omar Polo <op@omarpolo.com>
- Date:
make port number configurable