From 341bcc373da91a75e8a1b179ee5936ea0aa84491 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Fri, 27 Jul 2012 17:42:09 +0000 Subject: [PATCH] Remove #101: Forward known client headers in a predefined order The "predefined order" part is implemented and the randomization no longer strikes me as useful. --- TODO | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/TODO b/TODO index d8ef4a7f..7a289278 100644 --- a/TODO +++ b/TODO @@ -1,4 +1,4 @@ -$Id: TODO,v 1.65 2012/07/23 12:49:51 fabiankeil Exp $ +$Id: TODO,v 1.66 2012/07/27 17:37:43 fabiankeil Exp $ Some Privoxy-related tasks, sorted by the time they have been added, not by priority. @@ -289,11 +289,6 @@ http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO the win32 GUI. Integrate support for Privoxy-Regression-Test, Privoxy-Log-Parser, Privoxy-Filter-Test, uagen and similar tools. -101) Forward known client headers in a predefined order that can - be changed in the config file. Optionally use a random order. - Tools like p0f v3 use the header order for User-Agent detection - and thus changing the User-Agent doesn't fool them. - 102) Add an include directive to split the config file into several parts. 103) Potential performance improvement for large action files: -- 2.39.2