Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+0\/2\]\s+netfilter\:\s+allow\s+tab\s+character\s+in\s+SIP\s+headers\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+0\/2\]\s+netfilter\:\s+allow\s+tab\s+character\s+in\s+SIP\s+headers\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [PATCH 0/2] netfilter: allow tab character in SIP headers (score: 1): Author: Marco Angaroni <marcoangaroni@xxxxxxxxx>; Date: Wed, 7 Sep 2016 22:00:13 +0200; 2016-09-07 13:56 GMT+02:00 Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx>: Understood, thanks. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@x; /html/lvs-devel/2016-09/msg00004.html (8,918 bytes)
2. Re: [PATCH 0/2] netfilter: allow tab character in SIP headers (score: 1): Author: Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx>; Date: Wed, 7 Sep 2016 13:56:54 +0200; Applied this one too. I got confused because patch 0/x is usually the cover letter, I suggest you don't use 0/x for patch series in the future. Thanks! -- To unsubscribe from this list: send the line; /html/lvs-devel/2016-09/msg00003.html (10,354 bytes)
3. [PATCH 0/2] netfilter: allow tab character in SIP headers (score: 1): Author: Marco Angaroni <marcoangaroni@xxxxxxxxx>; Date: Tue, 30 Aug 2016 18:52:22 +0200; Current parsing methods for SIP headers do not allow the presence of tab characters between header name and header value. As a result Call-ID SIP headers like the following are discarded by IPVS SIP; /html/lvs-devel/2016-08/msg00015.html (10,323 bytes)

Current List: 1 - 3
Page: [1]