Olivier

Show:

What's happening?

  • Comment: Privoxy prematurely closes connections

    You got it! I tried with jcc.c v1.286, and I have no more problem. The log message now shows: > Done reading from server. Expected content length: 1. Actual content length: 1. Most recently received: 1. (my server is "slow", and typically returns small IP packets, so yes, privoxy might need multiples reads to get the whole headers) I consider this ticket "closed" Thanks!

    2009-09-07 08:02:06 UTC in Privoxy

  • Comment: Privoxy prematurely closes connections

    Thanks Fabian In the meanwhile, I'd like to have a try in debugging privoxy to see where could the problem come from (unfortunately I'm in a hurry). I retrieved the sources, and tried to compile/debug with MSVC. But the MSVC project files are for v6, and I have v9 (2008 C++ Express Edition), and the automatic MSVC conversion fails... Do you have any other MSVC project file that I could try ?...

    2009-08-21 09:51:42 UTC in Privoxy

  • Privoxy prematurely closes connections

    Hi I am using Privoxy 3.0.14 to access a proprietary web server (192.168.253.1) running on the same PC (WinXP) as Privoxy, and bound to a TAP-WIN32 interface (192.168.253.2). Privoxy systematically closes prematurely the connection, preventing the browser to retrieve the response data. Attached is a zip file including the corresponding log files: - get1-privoxy.pcap: wireshark traces showing...

    2009-08-19 09:26:30 UTC in Privoxy

  • Save project

    It would be nice to be able to save settings into a 'project file', which would include: - the file path or cd track # - the loop settings - speed & transposition settings This would avoid the hard task of redefining the loops each time you restart BP. Thanks anyway for your useful tool.

    2007-12-31 01:16:40 UTC in BestPractice

  • ENUMERATED identifiers are not accepted

    Enumeration with identifiers (and not named integer) is erroneously rejected by BN 1.5.2: TestEnum ::= ENUMERATED { yes, no, itdepends }.

    2007-10-08 20:31:59 UTC in BinaryNotes

  • ASN.1 constraints parsing errors

    BN 1.5.1 fails on the following type definitions which are all valid ASN.1: MyString ::= IA5String (PATTERN "[A-Z]*") MyInt ::= INTEGER { v1(1), v2(2) } (0..100) TestSeq ::= SEQUENCE (SIZE (10)) OF BOOLEAN TestSet ::= SET (SIZE (10)) OF BOOLEAN.

    2007-10-08 20:22:50 UTC in BinaryNotes

  • Support for Multiple-line comments

    ASN.1 2002 introduced Multiple-line comments using "/*" "*/" pairs. BN1.5.1 doesn't support this notation.

    2007-10-08 12:12:35 UTC in BinaryNotes

About Me


Send me a message