Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 1 subscriber
  • Views 2310 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

5.102 Runaway HTTP proxy

jeh
After up2date 5.102 the HTTP proxy still uses up 99,9% CPU. Looking at the new library I noticed a big difference in size, and the ownerships of libweed.so.0.0.0 is now 644, 507, users instead of 755, root, root. Is this correct or is this a little mistake?


This thread was automatically locked due to age.
Parents
  • 0
    Hello  jeh
    We think the Kaspersky Antivirus part of the HTTP Proxy is an endless field of trial and error and responsible for most of the strange HTTP  behaviours. With 5.101 it starts (undocumented) to use "Proxy-Connection keep-alive"  together with the use of HTTP "Proxy-Connection: close"  AND "Connection: close" (Why both?) it could confus your application/proxy as it does with ours.
Reply
  • 0
    Hello  jeh
    We think the Kaspersky Antivirus part of the HTTP Proxy is an endless field of trial and error and responsible for most of the strange HTTP  behaviours. With 5.101 it starts (undocumented) to use "Proxy-Connection keep-alive"  together with the use of HTTP "Proxy-Connection: close"  AND "Connection: close" (Why both?) it could confus your application/proxy as it does with ours.
Children