This is now applied to trunk as rev.13924
Amos
___
squid-dev mailing list
squid-dev@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev
On 10/02/2015 6:12 a.m., Kinkie wrote:
> Hi,
> I am not sure whether this is the most uptodate version of the
> patch; I'm auditing lp:~yadi/squid/parser-ng-requestline revno 13879.
>
Yes thats the latest right now.
> Short story, I can find nothing obviously evil with it - code is well
> docu
Hi,
I am not sure whether this is the most uptodate version of the
patch; I'm auditing lp:~yadi/squid/parser-ng-requestline revno 13879.
Short story, I can find nothing obviously evil with it - code is well
documented and intent is clear; as far as I understand Polygraph,
Coadvisor and my casual
This patch converts the request-line parse method from a char* string
parser to using ::Parser::Tokenizer based processing.
* the characters for each token are now limited to the RFC 7230
compliant values. The URI is taken as a whole token and characters which
are valid in only one sub-token segme
