HTTP Scanner killing connections to Rhodecode (server)

Discussion in 'ESET NOD32 Antivirus' started by cowwoc, Feb 4, 2013.

Thread Status:
Not open for further replies.
  1. cowwoc

    cowwoc Registered Member


    Environment: Windows 7 sp1, 64-bit,
    ESET AntiVirus 6.0.308.0
    Virus signature database: 7970 (20130204)
    Update module: 1041 (20120430)
    Antivirus and antispyware scanner module: 1379 (20130124)
    Advanced heuristics module: 1138 (20121210)
    Archive support module: 1158 (20121203)
    Cleaner module: 1059 (20121212)
    Anti-Stealth support module: 1038 (20130110)
    ESET SysInspector module: 1230 (2013010:cool:
    Real-time file system protection module: 1007 (20111129)
    Translation support module: 1100 (20121205)
    HIPS support module: 1065 (20130117)
    Internet protection module: 1051 (20121203)
    Database module: 1027 (20130129)

    Repro steps:
    1. Install and configure rhodecode from -- Rhodecode is a front-end for the Mercurial code repository system.
    2. Add a single repository to rhodecode
    3. Attempt to check out the repository using: "hg clone <url>" where <url> is the address of the repository you added.
    4. Mercurial will begin to check out the code but a few seconds in the connection will either hang or will die with "abort: connection ended unexpectedly"
    5. Disable ESET HTTP scanner and repeat step 3.
    6. Operation will complete successfully

    This problem is 100% reproducible. Side-note, I wasted an entire week (!!) before tracking this problem down to its source.

    Please consider adding a pop-up (similar to what we currently get when the signature files are updated) every time the HTTP scanner alters an HTTP stream. This would have saved me countless days and would have resulted in a quicker bug report.

  2. Marcos

    Marcos Eset Staff Account

    Do you have Windows updates KB2735855, KB2750841 and KB2789397 installed? If not, does installing them make a difference? You can also try this tweak.
  3. cowwoc

    cowwoc Registered Member


    Installing KB2789397 fixed the problem. I know this has been asked before, but do we expect Microsoft to release this to the general public in the form of a Windows Update in the future (since there will not be a sp2 release)?

    Thank you,
Thread Status:
Not open for further replies.