Check requests more carefully before serving them forcefully
authorFabian Keil <fk@fabiankeil.de>
Mon, 28 Dec 2015 18:55:49 +0000 (18:55 +0000)
committerFabian Keil <fk@fabiankeil.de>
Mon, 28 Dec 2015 18:55:49 +0000 (18:55 +0000)
commit8bb21add600416769cde743f11c19581e4539100
tree36f6cb124d8b5329cbedea31a2f25fe064a996c1
parent3e28dfdd76a773f824ea0d39ede00fa808f0f06c
Check requests more carefully before serving them forcefully

... when blocks aren't enforced.

Privoxy always adds the force token at the beginning
of the path, but would previously accept it anywhere
in the request line.

This could result in requests being served that should
be blocked. For example in case of pages that were
loaded with force and contained JavaScript to create
additionally requests that embed the origin URL
(thus inheriting the force prefix).

The bug is not considered a security issue and the
fix does not make it harder for remote sites to
intentionally circumvent blocks if Privoxy isn't
configured to enforce them.

Fixes #1695 reported by Korda.
jcc.c