Fixing issue mentioned below.
Fixing issue mentioned below.



From: 
Jesse Anderton <squishyent@gmail.com>
  To: 
Christian Grothoff <christian@grothoff.org>
  Date: 
Yesterday 11:50:56 pm
Christian,

I'm not sure whether this counts as a bug or not, but I found that if you
use MHD_OPTION_CIPHER_ALGORITHM or MHD_OPTION_PROTOCOL_VERSION in
MHD_start_daemon() without using MHD_USE_SSL a SIGSEGV will result.  This
signal is sent because the daemon's priority_cache member is dereferenced
in MHD_start_daemon_va(), but this member is only initialized if MHD_USE_SSL
is used.

This doesn't affect me: a workaround is easy.  I just wanted to make sure
you were aware of it.

Regards,

Jesse

pmq20/libmicrohttpd,slackner/libmicrohttpd,slackner/libmicrohttpd,slackner/libmicrohttpd,pmq20/libmicrohttpd,pmq20/libmicrohttpd