Suggestions for a ssl/proxy/http/authn server for the test suite?

[Lieven Govaerts]

Hi,

in order to further stabilize the serf code and avoid introducing
regressions in future serf releases, I'd like to expand the scope of
the test suite.

There are now 19 unit tests in test_all, but a lot of the code is not
covered. We don't have tests for ssl_buckets, compression,
authentication etc. The difficulty is that for testing a ssl_bucket
there needs to be a ssl-enabled server for the initial handshake to
work.

The small server we currently have in the serf test suite (now in
test/server) only does simple http responses. In order to test
compressed responses, ssl connections etc. this is largely
insufficient.

So, the idea is to embed a small web server in the test suite that has
the most common functionalities like ssl, gzip, basic/digest authn and
can act as a simple proxy. On top of that, we need to be able to get
the server to drop a connection on command, create malformed responses
(e.g. incorrect chunk lengths) etc.

I could implement those based on the new work-in-progress server code
in serf, but that's going to take a lot of time. Or, I can rely on an
installed apache webserver like the Subversion project does, but that
limits the options in controlling the responses, malformed responses
etc.

Any suggestions on how I can best proceed?

Lieven

[Justin Erenkrantz]

On Sat, Jun 18, 2011 at 3:02 AM, Lieven Govaerts <svn...@mobsol.be> wrote:
> Any suggestions on how I can best proceed?

Perhaps do a limited hybrid approach: use the custom C code for the
goofy protocol-twisting bits and use an installed httpd for the
overall functionality tests? -- justin