Fix for issue 857: RFC-7230 compliant forwarding of client certificates

2016-11-24 Thread Flemming Frandsen
e newlines is a much better solution than url encoding the newlines as less code (in my case none at all) is needed to deal with no newlines than urldecoding. -- Flemming Frandsen - YAPH - http://osaa.dk - http://dren.dk/ diff --git a/src/event/ngx_event_openssl.c b/src/event/ngx_event_openssl.c in

Re: Fix for issue 857: RFC-7230 compliant forwarding of client certificates

2016-11-24 Thread Flemming Frandsen
o fix up the url encoding patch that was posted earlier, though I still think it's silly to go to such lengths to preserve newlines that nobody wants. On Thu, Nov 24, 2016 at 2:39 PM, Maxim Dounin wrote: > Hello! > > On Thu, Nov 24, 2016 at 02:15:17PM +0100, Flemming Frandsen wrote:

Re: Fix for issue 857: RFC-7230 compliant forwarding of client certificates

2016-11-25 Thread Flemming Frandsen
s?) instead of newline + tab. This should be > compatible with what most servers provide as a result of parsing > multi-line header, and implies less changes. This needs an > additional investigation though. > I'd be very happy with this as the only change as my server already giv

Re: Fix for issue 857: RFC-7230 compliant forwarding of client certificates

2016-11-28 Thread Flemming Frandsen
gle space within the header value. -- Flemming Frandsen - YAPH - http://osaa.dk - http://dren.dk/ ___ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-devel