Commits
- Commit:
a5d822e542a927e88f655842273356225370c11f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
typo
- Commit:
be52e954c1d54f80485c643663db8e2ffc27510f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync readme.md with sandbox.c
- Commit:
3d132b283345475921bf9cf1e8d77e56ede2edf3
- From:
- Omar Polo <op@omarpolo.com>
- Date:
`param' is forbidden inside `location's too
and while there sort the list of disallowed rules.
- Commit:
2b520ad595f4ac7d438ace3abf2a0e2dd2fb78b5
- From:
- Omar Polo <op@omarpolo.com>
- Date:
misc improvements to the manual
- Commit:
efacb859a7ebc65cff1b51cff04cdc2aea3135e1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
change (again) the env/param separator: use '='
Given that env/param are new features of this release, no support for
the "old" syntax is needed.
- Commit:
762b9b991f373e5077d7e49396af62a34fa1c1ff
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add => in env/param and `port' between hostname and port for fastcgi
In the same spite of the last commit, add the missing separators
between strings to avoid the auto-concat pitfalls. `=>' is used to
separate between `env' and `param' arguments, while for `fastcgi' the
keyword `port' is required between the hostname/ip address and the
port (if provided).
Since `env', `param' and `fastcgi' are all new stuff, there's no need
to keep compatibility.
- Commit:
ff954a3e7641e83cca043ecc30789132478c7acd
- From:
- Omar Polo <op@omarpolo.com>
- Date:
typo...
- Commit:
d19951cf0373f6217bce2f97489bc46d6a8837ef
- From:
- Omar Polo <op@omarpolo.com>
- Date:
rename `mime MIME EXT' to `map MIME to-ext EXT'
With the newish automatic string concatenation, options like `mime'
that accepts two strings as parameter start to become ambiguous: which
strings gets concatenated? Instead of trying to document in the
manpage which argument(s) is subject to string concatenation, do the
concat always and introduce a separator. In the case of mime,
`to-ext' now acts as a separator to distinguish. While there, also
use a new keyword because it sounds better.
It's dead-easy to upgrade to the new configuration, possibly with some
sed magic, but for the moment the old `mime' form is preserved: (with
a warning!) Will be dropped in the next release.
- Commit:
d93c819182ba6decf8f7f1787c6ba416f76c315a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
use bsearch to match the keywords
not that it's a bottleneck, but it's fancier this way.
- Commit:
bffa7daab8d1a54cf099287cbc0ce443fea4c0d0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
provide a means to skip the runtime tests
Setting the environment variable SKIP_RUNTIME_TESTS to 1 will prevent
the runtime tests. This is useful when running the tests inside a
sandbox.
based on a similar diff by Anna "CyberTailor"
- Commit:
8c9b8f487e9efd3eab489d205fd55d97da34a6c3
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
replace add_{cflags,ldflags} with add_library
- Commit:
9c84a04f9cf948abc9d1c94e37a25a1f857b77b1
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
check freedesktop's libbsd
- Commit:
9797799ad4634887fa825388c9c1efe0be11f903
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
regress/Makefile: add missing LDFLAGS
- 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.