107 Commits

Author	SHA1	Message	Date
Omar Polo	6c6c7a0ed7	rename cgi_setpoll_on_* to cgi_poll_on_*	2020-12-28 18:01:06 +01:00
Omar Polo	3d9a1c73de	fixing prototype order	2020-12-28 09:57:58 +01:00
Omar Polo	4a28dd014a	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).	2020-12-28 09:55:56 +01:00
Omar Polo	6d91731552	fmt	2020-12-27 13:27:15 +01:00
Omar Polo	33d32d1fd6	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
Omar Polo	d5aba4c791	added missing copyright stuff	2020-12-24 16:49:55 +01:00
Omar Polo	488f059ac4	moving declarations to header file	2020-12-24 16:48:39 +01:00