You set errnossl in parseHTTP but not parseHTTPS... Which means it throws signal 11's unless the user provides an ErrNoSsl option in the config file.
I copied your initialization line from parseHTTP to parseHTTPS and it worked beautifully! Joe > -----Original Message----- > From: Peter van Dijk [mailto:[email protected]] > Sent: Thursday, January 28, 2010 8:38 AM > To: [email protected] > Subject: [Pound Mailing List] patch for telling users about https > > Hello, > > when used on ports other than 80 or 443, users may have a hard time > remembering whether a website/service > expects HTTP or HTTPS. Recent apache mod_ssl versions give users > attempting to talk > HTTP to a HTTPS port an informative error. > > http://hg.openpanel.com/pound-sslpatched/rev/90a2b1ae6bf4 is a patch > providing > the same for Pound. I've implemented the error similarly to other http > errors, with > full configuration support. Other than the removal of some already-dead > code > in http.c, I feel the patch is as minimal as possible. > > The patch is also attached to this message. > > Comments? > > Kind regards, > Peter van Dijk > OpenPanel > > > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
