Patch applied to trunk as r13853
On 01/14/2015 06:00 PM, Amos Jeffries wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/01/2015 7:21 a.m., Tsantilas Christos wrote:
I made all requested changes/fixes. The patch also ported to latest
trunk.
Okay, +1 for commit
FYI: Alex,
I am preparing this patch for commit, but I have many problems with
tests/testHttp1Parser tester.
The most of the problems caused because the changes I made in
Http1Parser aborts immediately parsing when no valid characters found
for the request method.
These problems can be fixed however
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/01/2015 12:31 a.m., Tsantilas Christos wrote:
I am preparing this patch for commit, but I have many problems
with tests/testHttp1Parser tester. The most of the problems caused
because the changes I made in Http1Parser aborts immediately
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/01/2015 7:21 a.m., Tsantilas Christos wrote:
I made all requested changes/fixes. The patch also ported to latest
trunk.
Okay, +1 for commit
FYI: Alex, kinkie, and myself had a debate on IRC and came to an
agreement for calling the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/2014 11:40 p.m., Tsantilas Christos wrote:
On 12/31/2014 09:54 AM, Alex Rousskov wrote:
On 12/30/2014 06:19 PM, Amos Jeffries wrote:
On 31/12/2014 7:30 a.m., Alex Rousskov wrote:
Amos, if on_first_request_error is converted into
Hi all,
I am posting a new patch. Sorry for the delay but the patch was a
little old, and many changes required..
This patch updated to apply to the latest squid sources, and uses the
new http parser.
This patch modify the http parser to reject a method which include non
alphanumeric
On 12/31/2014 02:31 PM, Alex Rousskov wrote:
On 12/31/2014 03:33 AM, Marcus Kool wrote:
On 12/31/2014 05:54 AM, Alex Rousskov wrote:
What would help is to decide whether we want to focus on
A) multiple conditions for establishing a TCP tunnel;
B) multiple ways to handle an
On 01/02/2015 09:16 AM, Marcus Kool wrote:
On 12/31/2014 02:31 PM, Alex Rousskov wrote:
On 12/31/2014 03:33 AM, Marcus Kool wrote:
On 12/31/2014 05:54 AM, Alex Rousskov wrote:
What would help is to decide whether we want to focus on
A) multiple conditions for establishing a TCP tunnel;
On 12/31/2014 05:54 AM, Alex Rousskov wrote:
[...]
What would help is to decide whether we want to focus on
A) multiple conditions for establishing a TCP tunnel;
B) multiple ways to handle an unrecognized protocol error; OR
C) multiple ways to handle multiple errors.
IMO, we want
On 12/31/2014 03:33 AM, Marcus Kool wrote:
On 12/31/2014 05:54 AM, Alex Rousskov wrote:
What would help is to decide whether we want to focus on
A) multiple conditions for establishing a TCP tunnel;
B) multiple ways to handle an unrecognized protocol error; OR
C) multiple ways to
On 10/21/2014 11:29 AM, Tsantilas Christos wrote:
- Adds on_first_request_error, a new ACL-driven squid.conf
directive
that can be used to establish a blind TCP tunnel which relays all bytes
from/to the intercepted connection to/from the intended destination
address. See the sketch above.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/2014 7:30 a.m., Alex Rousskov wrote:
On 10/21/2014 11:29 AM, Tsantilas Christos wrote:
- Adds on_first_request_error, a new ACL-driven squid.conf
directive that can be used to establish a blind TCP tunnel
which relays all bytes from/to
On 12/30/2014 06:19 PM, Amos Jeffries wrote:
On 31/12/2014 7:30 a.m., Alex Rousskov wrote:
On 10/21/2014 11:29 AM, Tsantilas Christos wrote:
- Adds on_first_request_error, a new ACL-driven squid.conf
directive that can be used to establish a blind TCP tunnel
which relays all bytes from/to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/10/2014 9:12 p.m., Tsantilas Christos wrote:
On 10/21/2014 04:29 PM, Amos Jeffries wrote:
2) All changes in src/tunnel.cc seem to be needless.
Some changes are required!
- tunnelStartShovelling() should *always* be the entrypoint to
14 matches
Mail list logo
