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!
Guys, just wanted to let you know that I updated Kaspersky to the latest
version and I can now checkout files even with all of the settings
enabled. So if you encounter the issue that I mentioned and you're
running Kaspersky AV, upgrade to the latest version.
Rey
Rey Bango wrote:
No prob.
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
Hey Sean,
Thanks for the suggestion. Unfortunately it didn't work but my DNS
resolution is much improved!! :)
The odd thing that I discovered last night is that my notebook PC (same
specs as above), which connects to my network wirelessly, can pull down
the repo with no problems. It seems i
I am able to pull a copy using: svn checkout
*http*://jqueryjs.googlecode.com/svn/trunk/
jqueryjs
I'm not sure why you are getting that error though. Perhaps it is a DNS
issue? You could try switching you DNS to openDNS.com
~Sean
HTTPS is the only way that I can checkout code, so I have not seen
that error myself. I set TortoiseSVN to remember my password so it
never prompts me anyway.
On May 22, 11:45 am, Rey Bango <[EMAIL PROTECTED]> wrote:
> Hi Sam. Thanks for the suggestion but I'm only pulling down and not
> committi
Hi Sam. Thanks for the suggestion but I'm only pulling down and not
committing anything. So HTTP is supposed to work for that.
With HTTPS, I'm prompted for a login which I don't need at the moment.
Rey...
Sam Collett wrote:
Have you tried using https? I don't think you can check in using
no
Have you tried using https? I don't think you can check in using
normal http.
On May 21, 7:20 pm, Rey Bango <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> When I try checkout using TortoiseSVN (latest)
> viahttp://jqueryjs.googlecode.com/svn/trunk/, I get the following error:
>
> Error: REPORT reques
13 matches
Mail list logo