On Tue, 2008-10-21 at 11:21 -0700, Nigel Kersten wrote: > On Tue, Oct 21, 2008 at 9:28 AM, Robert Segall <[EMAIL PROTECTED]> wrote: > > On Mon, 2008-10-20 at 08:12 -0700, Nigel Kersten wrote: > >> [EMAIL PROTECTED]:/src/Pound-2.4.3 $ ./configure --help |grep cert1 > >> --enable-cert1l enable or disable single-line certificate > >> (default: disabled) > >> > >> Sorry I've taken so long to get around to testing this patch I > >> requested a while ago, but there seem to be some problems with it. > >> > >> Although all transactions appear to work correctly with Mongrel and > >> single-line certificates, I get this in the logs: > >> > >> pound: (400c2960) line too long: Sep 19 15:50:01 2013 GMT > >> pound: (400c2960) line too long: CN = > >> 2ac28920-d223-4f61-b937-ee9869103f91 > >> pound: (400c2960) line too long: CN = host.mydomain.com > >> > >> >From looking at the source, I think these errors aren't disastrous, > >> and the code that checks whether MAXBUF is exceeded simply doesn't > >> take into account the --enable-cert1l behavior, but I'm not positive. > > > > I'm not clear where this should happen, unless your host returns this > > header OR it was sent by the client. The header is generated by Pound, > > and is NOT of limited length. > > What would you like me to provide to work out where the issue lies Robert?
If you look at the source, you'll notice that the certificate is written to the back-end regardless of line length. The message you see is generated when Pound see a certificate-type line on input, which should never happen. I suggest you sniff the sockets between the client and Pound, as well as Pound to back-end, to see where the header is generated. We'll take it from there. -- Robert Segall Apsis GmbH Postfach, Uetikon am See, CH-8707 Tel: +41-44-920 4904 -- To unsubscribe send an email with subject unsubscribe to [EMAIL PROTECTED] Please contact [EMAIL PROTECTED] for questions.
