Commits
- Commit:
9862b637c2aa97e7e8d148ae9c3f92d0ca758fa7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
track handshakes
This alter the current state machine by adding S_HANDSHAKE as the
initial state. There, we ensure we did the handshake and we check
SNI. ATM we simply continue in S_OPEN, but later we can add virtual
host checks there, and skip to S_INITIALIZING with an error state if
the client is accessing a wrong host.
- Commit:
0d7a38c4ce99cf5367a242d0a1d41b51d4a742e8
- From:
- Omar Polo <op@omarpolo.com>
- Date:
avoid __dead and return at the end of main
- Commit:
796c6e75d72a1fbd8ea1dd6ccaaaa57180eb3865
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix build on non-OpenBSD systems
not every system has a __dead attribute for functions. This fixes the
build on FreeBSD.
- Commit:
7b1d97903280066059ed4b00d4d407876957d071
- From:
- Omar Polo <op@omarpolo.com>
- Date:
reject non-gemini protocols with 53
- 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:
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:
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:
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:
6c6c7a0ed7de7ec3c4329c6f9892862a4f065451
- From:
- Omar Polo <op@omarpolo.com>
- Date:
rename cgi_setpoll_on_* to cgi_poll_on_*
- Commit:
3d9a1c73de100ab3f6207af3700121e9a3607a1b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fixing prototype order
- 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:
6d91731552a1be86794a0164b9c8313e0631725d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fmt
- 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?).