Commits
- Commit:
6084a9a5ba263ddc8cd67f7e03f2ee0481d4ea77
- From:
- Omar Polo <op@omarpolo.com>
- Date:
prefer sizeof(x) instead of datalen
- Commit:
72b033ef18ae3f82922f6f11ce0f5194e95f667d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add ability to proxy requests
Add to gmid the ability to forwad a request to another gemini server and
thus acting like a reverse proxy. The current syntax for the config
file is
server "example.com" {
...
proxy relay-to host:port
}
Further options (like the use of custom certificates) are planned.
cf. github issue #7
- Commit:
5eb3fc905f5e3bd2f2d586fb1e0ceda879500b3e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't work around a missing -Wno-unused-parameter
It's been there for a long time, and it's frankly annoying to pretend
to use parameters. Most of the time, they're there to satisfy an
interface and nothings more.
- Commit:
4cd25209651f224be8c34d6006ef689963ce37d5
- From:
- Omar Polo <op@omarpolo.com>
- Date:
one FastCGI connection per client
FastCGI is designed to multiplex requests over a single connection, so
ideally the server can open only one connection per worker to the
FastCGI application and that's that.
Doing this kind of multiplexing makes the code harder to follow and
easier to break/leak etc on the gmid side however. OpenBSD' httpd
seems to open one connection per client, so why can't we too?
One connection per request is still way better (lighter) than using
CGI, and we can avoid all the pitfalls of the multiplexing (keeping
track of "live ids", properly shut down etc...)
- Commit:
403c42204182515d7281d8c11084eef596f8a6ee
- From:
- Omar Polo <op@omarpolo.com>
- Date:
[cgi] switch from pipe(2) to socketpair(2)
We can't use normal pipe(2)s with libevent in some cases. Switch to
socketpair(2), which doesn't have the same problem.
This has the drawback that it doesn't prevent the CGI script from
reading stdout, for instance. (sockets are two-way, pipes only one-way)
- Commit:
2e2e189b016fe981fcb32e2c461a7c385cb25942
- From:
- Omar Polo <op@omarpolo.com>
- Date:
PF_UNIX is not a valid protocol for socketpair
OpenBSD accept it, but FreeBSD disallows it. PF_UNSPEC (or 0) should
be used instead. The FastCGI bit in the regress suite still doesn't
work on FreeBSD, but at least now it starts.
- Commit:
e7c6502bf3ebe199349e315ac7f112db6a2db38e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't leak a file descriptor
make sure we always close every fd in every possible code path; while
there, also add a log_err if fork(2) failed.
- Commit:
ea976e8743ad3b3263faae00d88e40bcf727097d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't let CGI scripts inherit our stderr
our stderr could have been sent to the logger process, so it may be
invalid. Furthermore, in the future we may want to capture also the
stderr of the processes.
- Commit:
ce2c9edbc230a052627540e3fd0f8a8b190be850
- From:
- Omar Polo <op@omarpolo.com>
- Date:
define and use GMID_VERSION
- Commit:
1feaf2a618ee1c4771fee80ced7acf31fe40fdae
- From:
- Omar Polo <op@omarpolo.com>
- Date:
use the correct document root
pass the correct loc_off to the executor, so the various variables
that depends on the matched location (like DOCUMENT_ROOT) are computed
correctly.
- Commit:
8ad1c570242cd93f0802931621b49b2510b338e7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fastcgi: a first implementation
Not production-ready yet, but it's a start.
This adds a third ``backend'' for gmid: until now there it served
local files or CGI scripts, now FastCGI applications too.
FastCGI is meant to be an improvement over CGI: instead of exec'ing a
script for every request, it allows to open a single connection to an
``application'' and send the requests/receive the responses over that
socket using a simple binary protocol.
At the moment gmid supports three different methods of opening a
fastcgi connection:
- local unix sockets, with: fastcgi "/path/to/sock"
- network sockets, with: fastcgi tcp "host" [port]
port defaults to 9000 and can be either a string or a number
- subprocess, with: fastcgi spawn "/path/to/program"
the fastcgi protocol is done over the executed program stdin
of these, the last is only for testing and may be removed in the
future.
P.S.: the fastcgi rule is per-location of course :)
- Commit:
fdea6aa0bca24f6f947e2126ce101fd59caa7a31
- From:
- Omar Polo <op@omarpolo.com>
- Date:
allow ``root'' rule to be specified per-location block
- Commit:
9cc630aa63cfd22553912b5a1fc41a71776cb272
- From:
- Omar Polo <op@omarpolo.com>
- Date:
added ``env'' option to define environment vars for CGI scripts
- Commit:
3841a3693094ae7cc3cfd4f80da7f463e2756bcc
- From:
- Omar Polo <op@omarpolo.com>
- Date:
restore signal handlers before exec'ing CGI scripts
- Commit:
89541eeec019626df4651f44b90df6a31a844dab
- From:
- Omar Polo <op@omarpolo.com>
- Date:
define TLS_VERSION, TLS_CIPHER and TLS_CIPHER_STRENGTH for CGI scripts