TortoiseSVN trunk checkout“服务器发送了意外的返回值(403 Forbidden)以响应选项”错误

发布于 2024-08-27 06:31:17 字数 333 浏览 11 评论 0原文

我的问题是,每次我使用如下 URL 进行某些操作时: https://nttt.dttt.com:8443/svn/nttt/Med/trunk 我明白了

服务器发送了意外的返回值(403 Forbidden)以响应“OPTIONS”。

我提供的用户和密码是正确的,所以没有问题。

我不知道问题出在哪里,我不知道是否是服务器的问题(对女巫我没有任何控制权)或我的乌龟客户。

My problem is that every time I do some operation with an URL like the following one: https://nttt.dttt.com:8443/svn/nttt/Med/trunk I get

Server sent unexpected return value (403 Forbidden) in response to OPTIONS".

The user and password I supplied was correct, so no problem there.

I don't know where the problem lies, I don't know if it is the server(on witch I don't have any control) or my Tortoise client.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(11

等待我真够勒 2024-09-03 06:31:17

我不认为这是 TroitoiseSVN。最有可能的问题是您无权访问完整的树或所有 HTTP 操作。尝试在浏览器中访问以下 URL:

https://nttt.dttt.com:8443/svn/nttt

https://nttt.dttt.com:8443/svn/nttt/Med

https://nttt.dttt.com:8443/svn/nttt /Med/trunk

看看是否收到任何 403 错误。否则,您将需要与系统管理员联系以修复权限。

I don't think it is TroitoiseSVN. The problem most likely is that you don't have access to full tree or all HTTP operations. Try accessing these URLs in your browser:

https://nttt.dttt.com:8443/svn/nttt

https://nttt.dttt.com:8443/svn/nttt/Med

https://nttt.dttt.com:8443/svn/nttt/Med/trunk

And see if you get any 403 errors. Otherwise you will need to talk to your system administrator to fix the rights.

几度春秋 2024-09-03 06:31:17

如果您使用不同的帐户签出 SVN 存储库,则可能会发生此错误。帐户数据存储到磁盘,下次您要提交到存储库时,SVN 可能会使用错误的帐户。它可以帮助在控制台或终端中指定正确的帐户:

svn commit -m "my message" --username my_username --password my_password

This error can happen if you checkout a SVN repository with a different account. The account data is stored to disk, and the next time you want to commit to a repository SVN may use the wrong account. It could help to specify the right account in the console or terminal:

svn commit -m "my message" --username my_username --password my_password
紫轩蝶泪 2024-09-03 06:31:17

根据这篇文章,这是一个已知错误 http://groups .google.com/group/visualsvn/browse_thread/thread/e16fe2e3c5fdab8d?pli=1
手动设置用户名和密码可能会有所帮助

according to this post it is a known bug http://groups.google.com/group/visualsvn/browse_thread/thread/e16fe2e3c5fdab8d?pli=1
Setting username and password manually may help

请恋爱 2024-09-03 06:31:17

您只需从 SVN 中删除保存的数据即可。转到此路径所有程序 --> TSVN -->设置 --> 保存的数据 --->清除验证数据。执行此操作后,您可以使用正确的凭据访问 SVN 路径。

You just need to delete the saved data from your SVN. Go to this path All Programs --> TSVN --> settings -->Saved Data ---> Clear the Authentication Data. After doing this, you can access to your SVN path with the proper credentials.

空‖城人不在 2024-09-03 06:31:17

您可能使用了错误的 URL。您的 apache 服务器也可能配置错误。

当您将该 URL 输入网络浏览器时会发生什么?你能看到吗?首先尝试通过使用浏览器测试您的 URL 来验证路径,然后再次尝试 Tortoise。

It's possible that you're using the wrong URL. It's also possible that your apache server is misconfigured.

What happens when you put that URL into your web browser? Can you see it? Try verifying the path first by testing your URL with the browser, then try Tortoise again.

兔姬 2024-09-03 06:31:17

我也在调试这个问题。我可以控制服务器。因此,刚刚发现组“所有人”(如果存在)被配置为“无访问权限”(我就是这么做的),并且它与我的管理权限相冲突,因此只需将其完全删除即可解决此禁止的用户错误。

i was also debugging this issue. I have a control over the server. So just found out that the group "everyone", if present, was configured to "No Access" (which I did it) and it was conflicting with my admin rights so just removed it completely to resolve this forbidden user error.

吖咩 2024-09-03 06:31:17

我遇到了同样的问题,并将 TortoiseSVN 更新到最新可用版本(目前为 1.8.10)解决了这个问题。

我曾经运行1.6.x。

I had the same problem and solved it updating TortoiseSVN to last version avaliable (1.8.10 at the moment).

I used to run 1.6.x.

半世晨晓 2024-09-03 06:31:17

我刚才在尝试更新我的工作副本时遇到了相同的错误消息。

因为我知道需要更新哪个目录,所以我尝试更新该目录并且它起作用了(奇怪的是)。

之后,这个问题似乎暂时消失了。我真的不明白发生了什么事。

回顾一下:我试图更新一个根目录位于的存储库

    https://MyServer/repos/config/MyProject/trunk

,它抱怨

    svn: Server sent unexpected return value (403 Forbidden) in response
    to OPTIONS request for 'https://MyServer/repos/config'

我这样做了,然后

    cd $WORKINGCOPY/path/to/my/changed/dir
    svn up ... https://MyServer/repos/config/path/to/my/changed/dir/ .

这有效了。

任何以下 svn up 现在都可以工作。

I had the same error message just now when trying to update my working copy.

As I knew which directory needed to be updated, I tried to update just that and it worked (Strangely enough).

After that, it seems the issue is gone for the moment. I really do not understand what was going on.

To recap: I was trying to update a repository having its root at

    https://MyServer/repos/config/MyProject/trunk

and it was complaining

    svn: Server sent unexpected return value (403 Forbidden) in response
    to OPTIONS request for 'https://MyServer/repos/config'

I did then an

    cd $WORKINGCOPY/path/to/my/changed/dir
    svn up ... https://MyServer/repos/config/path/to/my/changed/dir/ .

and this worked.

Any following svn up now works.

山色无中 2024-09-03 06:31:17

如果您没有存储库的读/写权限,则 403 会作为响应,您可能只有读权限,并且您正在尝试提交更改,因此您不被允许
在这种情况下,您需要咨询您的系统管理员,以根据您的角色

和 权限授予您适当的特权和权限
我不知道这是服务器(我对其没有任何控制权)还是我的乌龟客户端。

您的客户端很好,只是需要考虑服务器权限

that 403 comes in response if you don't have permissions on the repository to Read/Write you may only have Read permissions and you're trying to commit changes so you're not allowed
well in this case you need to consult with your system administrator to allow you proper privileges and permissions according to you role

and
I don't know if it is the server(on which I don't have any control) or my Tortoise client.

your client is just fine only server permissions needs a consideration

末が日狂欢 2024-09-03 06:31:17

如果这个问题只出现在大文件量的情况下怎么办?提交通常适用于单个文件夹或包含某些文件的文件夹,但当它是一个大层次结构时,该过程会在完成提交之前启动和停止,并显示错误消息。

What if this problem appears only for big amount of files. The commit works normally for one single folder, or a folder including some files, but when it's a big hierarchy, the process starts and stops with the error message just before completing the commit.

骷髅 2024-09-03 06:31:17

我最近有同样的错误消息。经过检查,我意识到我在 URL 中使用了错误的项目名称。可能也值得检查您的网址。

I recently had the same error message. After checking, I realized that I was using a bad project name in the URL. Might be worth checking your URL too.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文