Commits

Commit:
611dffe81628683ebd2b48ae6f02f9bff6081ee9
From:
Omar Polo <op@omarpolo.com>
Date:
remove regress/sha we can use cmp to tell if two files are different, which also has the benefit of being available everywhere and reporting the byte offset of the first difference. Reduces the test dependencies on some systems.
diff | patch | tree
Commit:
9adeb265792f0049321c34bf9e32674b0be65942
From:
Omar Polo <op@omarpolo.com>
Date:
re-establish fastcgi test
diff | patch | tree
Commit:
a5fb2593a9ab1c6cc4ae027924724dd2714f7fe1
From:
Omar Polo <op@omarpolo.com>
Date:
adjust regress to use `ge' for the old configless test
diff | patch | tree
Commit:
d29a2ee2246e1b1b0c5222a823820e42422c894e
From:
Omar Polo <op@omarpolo.com>
Date:
get rid of the CGI support I really want to get rid of the `executor' process hack for CGI scripts and its escalation to allow fastcgi and proxying to work on non-OpenBSD. This drops the CGI support and the `executor' process entirely and is the first step towards gmid 2.0. It also allows to have more secure defaults. On non-OpenBSD systems this means that the sandbox will be deactivated as soon as fastcgi or proxying are used: you can't open sockets under FreeBSD' capsicum(4) and I don't want to go thru the pain of making it work under linux' seccomp/landlock. Patches are always welcome however. For folks using CGI scripts (hey, I'm one of you!) not all hope is lost: fcgiwrap or OpenBSD' slowcgi(8) are ways to run CGI scripts as they were FastCGI applications. fixes for the documentation and to the non-OpenBSD sandboxes will follow.
diff | patch | tree
Commit:
d45d5306e3c077eb3c8ecfc4c60e2e427b4cc21d
From:
Omar Polo <op@omarpolo.com>
Date:
fix test_auto_index
diff | patch | tree
Commit:
475205fa0f2737475a17dd692b71611523b898a0
From:
Omar Polo <op@omarpolo.com>
Date:
check for the expected page in test_auto_index not just the number of lines, check the full page!
diff | patch | tree
Commit:
9448a01fdb793e37f805f3246676f853f69d1766
From:
Omar Polo <op@omarpolo.com>
Date:
use the types block instead of `map' in the tests too
diff | patch | tree
Commit:
91971201e545529098ac2b9bc374a383a637e28f
From:
Omar Polo <op@omarpolo.com>
Date:
break out if check_reply fails it's not a problem when we have only one check_reply at then end, since $? is kept across function boundaries, but when we have multiple checks we need to quit on the first error.
diff | patch | tree
Commit:
fb1212266f366f457b0c142869b8095213fc5b96
From:
Omar Polo <op@omarpolo.com>
Date:
add tests for the type block
diff | patch | tree
Commit:
901905e0cf0f5f141461df7ea199711ea951c919
From:
Omar Polo <op@omarpolo.com>
Date:
bail out of client_read if we've already decide what to do libevent2 can still somehowe call client_read even in code paths that never enable reading from the evbuffer. Can't reproduce on the libevent in base on OpenBSD. It's a bit ugly, but it's a small workaround for something that otherwise *always* make gmid crash when linked against libevent2. (client_read works under the assumption that c->host != NULL, matched_proxy crashes otherwise.)
diff | patch | tree
Commit:
92a9f41d3d4633cc8afbcef12d2dbd3743ac300d
From:
Omar Polo <op@omarpolo.com>
Date:
add set_proxy to simplify testing + more checks in test_proxy_with_certs
diff | patch | tree
Commit:
e19f21f5a65dab4520d10f600df86ec36e80ec22
From:
Omar Polo <op@omarpolo.com>
Date:
parethesize `proxy', I'm about to change the syntax
diff | patch | tree
Commit:
c064f3de1d3eac4784f185dce4ddf029e0429ead
From:
Omar Polo <op@omarpolo.com>
Date:
add proxying with client certificate test
diff | patch | tree
Commit:
e6ab6b25fce38c8f1d700becea395ae41ced1555
From:
Omar Polo <op@omarpolo.com>
Date:
typo
diff | patch | tree
Commit:
4b5b1e82a9459f7b4c11a31da4409c5b527730e8
From:
Omar Polo <op@omarpolo.com>
Date:
add a test for the `proxy relay-to' rule
diff | patch | tree