Commits
- Commit:
15902770073dd67df3a9af0f6da7d63bfb031d72
- From:
- Omar Polo <op@omarpolo.com>
- Date:
conf & vhosts
* gmid.c (main): changed behaviour: daemon off by default
(main): changed -c in -C (cert option)
(main): changed -k in -K (key option, for consistency with -C)
(main): added -c to load a configuration
(main): certs, key and doc (-C -K and -d) doesn't have a default value anymore
(handle_handshake): add vhosts support
- Commit:
b9220ca4de556f24be9cdc0d478109b75cd476ae
- From:
- Omar Polo <op@omarpolo.com>
- Date:
new README + wording in manpage
- Commit:
85dff1f9c3b18256f0f2cceb802c3c7f2961bc58
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix remote_user for CGI and add -6 flag to enable ipv6
- 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:
00781742c5578afa15d0b2dbc86adf47870fb94f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
reject %00
- Commit:
df6ca41da36c3f617cbbf3302ab120721ebfcfd2
- From:
- Omar Polo <op@omarpolo.com>
- Date:
IRI support
This extends the URI parser so it supports full IRI (Internationalized
Resource Identifiers, RFC3987). Some areas of it can/may be improved,
but here's a start.
Note: we assume UTF-8 encoded IRI.
- Commit:
043acc97b16be18d85bb1914da50f7ce2aa2623e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
mention the %2F caveat
- Commit:
83000e2dd417e81dabfcad740af63d1ee86e1389
- From:
- Omar Polo <op@omarpolo.com>
- Date:
improve wording
"concurrently" means at the same time, which can be confusing when we
say that it's single-threaded on a single process.
- 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:
721e2325296b1556eb0d2224ef37b387091dff43
- From:
- Omar Polo <op@omarpolo.com>
- Date:
make port number configurable
- Commit:
a5d310bc0d07fea3d75b593ea6b2f86dad006211
- From:
- Omar Polo <op@omarpolo.com>
- Date:
[cgi] added support for path parameters
enhance the CGI scripting support so that script can take path
parameters. That is, a script at /cgi/foo is called when the request
path is /cgi/foo/bar/...
This commit also introduce some backward incompatible changes as the
default env variables set for the CGI script changed.
- Commit:
0ed56567950c521041674b3e255147b6d6bea03e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
documentation improvements
- Commit:
72342dc9606a0283490a3a9283d2ed2d31888eeb
- From:
- Omar Polo <op@omarpolo.com>
- Date:
implementing CGI – NOT READY YET!
This is a first try at implementing CGI scripting. The idea is that,
if CGI is explicitly enabled by the user, when a user requires an
executable file instead of serving it to the client, that file will be
executed and its output fed to the client.
There are various pieces that are still lacking, the firsts that comes
to mind are:
- performance: the handle_cgi just loops ignoring the
WANT_POLLIN/POLLOUT and blocking if the child process hasn’t
outputted anything.
- we don’t parse query variable (yet)
- we need to set more variables in the child environment
side question: it’s better to set the variables using setenv() or
by providing an explicit environment?
- document what environment the CGI script will get
- improve the horrible unveil/pledge(cgi ? …)
but now I can serve “hello-world”-tier script from gmid!
- Commit:
2c3a40faf850ad608abf87f928a11fb4fba3057b
- From:
- Omar Polo <op@omarpolo.com>
- Date:
added option to log to a file