The folks at Google wrote this:
"If the repository was accessible in your browser and not via the svn
client, I'll bet that the AV program just didn't understand DAV HTTP
traffic."
Once I upgraded Kaspersky AV to its latest version, the issue went away
so it looks like some other Kaspersky mus
Hey Rey,
taking a wild guess here, but maybe they use a slightly different
port than other svn repos, and maybe your AV program was blocking
traffic through that port? Kind of like how some AV / firewall
programs block ports used for BitTorrent?
Anyway, really glad you got it worked out!
No prob. Hopefully it won't happen to anyone else but at least there's a
solution. I plan on contacting Kasperky on this.
I'm just curious as to why this only effects Googles SVN repos.
Rey
Brandon Aaron wrote:
Glad you were able to get it worked out. Thanks for sharing the solution.
--
B
Rey Bango wrote on 5/23/2007 9:21 AM:
Well, I figured it out and it was Kasperky AV.
A sign of the times when AV products cause more harm than the actual viruses:
"The update of Norton's virus database on Friday has caused millions of PCs and
computers to crash, a heavy blow to people's dai
That's great news. Thanks for the feedback Rey.
~Sean
Glad you were able to get it worked out. Thanks for sharing the solution.
--
Brandon Aaron
On 5/23/07, Rey Bango <[EMAIL PROTECTED]> wrote:
Hi guys,
Well, I figured it out and it was Kasperky AV. Here's what I had to do.
In the Anti-Spy section, I had to uncheck "Enable Anti-Phishing"
In th
Hi guys,
Well, I figured it out and it was Kasperky AV. Here's what I had to do.
In the Anti-Spy section, I had to uncheck "Enable Anti-Phishing"
In the Web Anti-Virus section, I had to uncheck "Scan HTTP traffic"
I'm not quite sure why these two options were interfering with SVN
checkout fro
7 matches
Mail list logo
