Menu

#1139 Connection to pic.ipicture.ru brokes second after initiated

3.0.x
closed
other (323)
5
2014-08-14
2009-04-29
Anonymous
No

Without Privoxy all works fine but with it connections closed second after them initiated. Sometimes it sends HTML page "Connection failed" in plain text. Other hosts seems work fine. There is log:

Apr 30 00:33:10.109 00001690 Request: pic.ipicture.ru/uploads/090427/41004/thumbs/6s2FHr5RT3.jpg
Apr 30 00:33:11.546 00001690 Error: read from: pic.ipicture.ru failed: WSAECONNRESET - Connection reset by peer.
Apr 30 00:33:11.671 00001264 Request: pic.ipicture.ru/uploads/090427/41004/thumbs/04zt4SV7dP.jpg
Apr 30 00:33:13.093 00001264 Error: read from: pic.ipicture.ru failed: WSAECONNRESET - Connection reset by peer.
Apr 30 00:33:13.109 00001264 Error: Already forwarded the original headers. Unable to tell the client about the problem.
Apr 30 00:33:13.234 00000814 Request: pic.ipicture.ru/uploads/090427/41004/thumbs/fGcTkad353.jpg
Apr 30 00:33:14.687 00000814 Error: read from: pic.ipicture.ru failed: WSAECONNRESET - Connection reset by peer.
Apr 30 00:33:14.828 00000830 Request: pic.ipicture.ru/uploads/090427/41004/thumbs/TrHpfz5222.jpg
Apr 30 00:33:16.250 00000830 Error: read from: pic.ipicture.ru failed: WSAECONNRESET - Connection reset by peer.
Apr 30 00:33:16.250 00000830 Error: Already forwarded the original headers. Unable to tell the client about the problem.
Apr 30 00:33:16.390 00000894 Request: pic.ipicture.ru/uploads/090427/41004/thumbs/4g1S6R6sh4.jpg
Apr 30 00:33:17.890 00000894 Error: read from: pic.ipicture.ru failed: WSAECONNRESET - Connection reset by peer.
Apr 30 00:33:18.031 00000ec4 Request: pic.ipicture.ru/uploads/090428/41004/thumbs/cUTaa2PEnt.jpg
Apr 30 00:33:19.500 00000ec4 Error: read from: pic.ipicture.ru failed: WSAECONNRESET - Connection reset by peer.
Apr 30 00:33:19.500 00000ec4 Error: Already forwarded the original headers. Unable to tell the client about the problem.
Apr 30 00:33:19.640 00001008 Request: pic.ipicture.ru/uploads/090428/41004/thumbs/vJ9Q7b0wDb.jpg
Apr 30 00:33:21.062 00001008 Error: read from: pic.ipicture.ru failed: WSAECONNRESET - Connection reset by peer.
Apr 30 00:33:21.203 00001528 Request: pic.ipicture.ru/uploads/090428/41004/thumbs/H6iXeIcU3U.jpg
Apr 30 00:33:22.625 00001528 Error: read from: pic.ipicture.ru failed: WSAECONNRESET - Connection reset by peer.
Apr 30 00:33:22.625 00001528 Error: Already forwarded the original headers. Unable to tell the client about the problem.

Version: 3.0.12.
OS: Windows XP SP2
Browsers: IE7, Opera 9.63
Firewall: Outpost 3.51
Another proxy: Handy cache - it's forward requests to Privoxy

Mail: lindaoneesama@gmail.com

Discussion

  • Fabian Keil

    Fabian Keil - 2009-04-29

    Is this reproducible?
    Does it work if you temporarily disable your "Firewall"?

     
  • Fabian Keil

    Fabian Keil - 2009-04-29
    • assigned_to: nobody --> fabiankeil
    • status: open --> pending
     
  • Nobody/Anonymous

    • status: pending --> open
     
  • Nobody/Anonymous

    Yes. Even if I unload it I can reproduce this.

     
  • Fabian Keil

    Fabian Keil - 2010-07-12

    Can you reproduce the problem with Privoxy 3.0.16 or newer?

     
  • Fabian Keil

    Fabian Keil - 2010-07-12
    • status: open --> pending
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB