发表文章

[Objective-C] 同步 webdav URL 错误 "无法打开此文件夹。请确保它存在 " sync webdav URL error "Unable to open this folder. Please make sure it exists"[ios]

pixelseventy2 2017-10-9 76

重现的步骤

  1. 在 iOS 上登录到 owncloud 服务器
  2. 打开文件夹
  3. 获取消息 "无法打开此文件夹。请确保它存在 "

预期行为

文件夹应打开并浏览

实际行为

您收到消息 "无法打开此文件夹。请确保它存在 "

服务器配置

Web 服务器:
CentOS 7, Owncloud 运行在文件夹/Owncloud/。 如果使用重写规则直接/* 到/owncloud, 仍然会出现错误

数据库:
MySQL, 在单独的服务器上。
PHP 版本:
5.4.16

客户端

iOS 版本:
9.3.4-客户端设置为使用服务器地址, 包括/owncloud/

ownCloud 应用程序版本:
3.5。0

设备型号:
Ipad Pro 9。7

日志

Web 服务器错误日志

没有重定向:
192.168.0.185-[10/9月/2016:16:14:12 + 0100] "获取/owncloud/状态. php HTTP/1.1" 200 96
192.168.0.185-[10/9月/2016:16:14:13 + 0100] "PROPFIND/远程. php/webdav/HTTP/1.1" 404 216
192.168.0.185-[10/9月/2016:16:14:18 + 0100] "PROPFIND/远程. php/webdav/p/webdav/密码/HTTP/1.1" 404 235
192.168.0.185-[10/9月/2016:16:14:21 + 0100] "PROPFIND/遥控. php/webdav/p/webdav/个人/HTTP/1.1" 404 234

使用重定向:
192.168.0.185-[10/9月/2016:16:14:52 + 0100] "PROPFIND/远程. php/webdav/HTTP/1.1" 302 246
192.168.0.185-克里斯 [10/9月/2016:16:14:52 + 0100] "PROPFIND/owncloud/远程. php/webdav/HTTP/1.1" 207 12168
192.168.0.185-克里斯 [10/9月/2016:16:14:53 + 0100] "获取/owncloud/ocs/v1. php/应用程序/files_sharing/api/v1/共享?路径 = & 子 = 真 HTTP/1.1" 200 1083
192.168.0.185-[10/9月/2016:16:15:14 + 0100] "PROPFIND/远程. php/webdav/p/webdav/密码/HTTP/1.1" 302 265
192.168.0.185-克里斯 [10/9月/2016:16:15:14 + 0100] "PROPFIND/owncloud/远程. php/webdav/p/webdav/密码/HTTP/1.1" 404 246

ownCloud 日志 (数据/ownCloud 日志)

未生成日志

告诉我们什么可以改进:

iOS 应用程序尝试连接, 假设 OC 在根中运行, 而不管服务器 URL 设置为什么。 它也腐化的 URL 时, 连接;在上面的 webdav url 中看到额外的 "/p/webdav"。 如果 owncloud 在根中运行, 则不会发生这种情况。

原文:

Steps to reproduce

  1. Log in to owncloud server on iOS
  2. Open folder
  3. Get the message "Unable to open this folder. Please make sure it exists"

Expected behaviour

Folder should open and be browseable

Actual behaviour

You get the message "Unable to open this folder. Please make sure it exists"

Server configuration

Web server:
CentOS 7, Owncloud is running under the folder /owncloud/. Errors still occur if using a rewrite rule to direct /* to /owncloud/*

Database:
MySQL, on separate server.
PHP version:
5.4.16

Client

iOS version:
9.3.4 - Client is set to use a server address including the /owncloud/

ownCloud app version:
3.5.0

Device model:
Ipad Pro 9.7

Logs

Web server error log

Without redirect:
192.168.0.185 - - [10/Sep/2016:16:14:12 +0100] "GET /owncloud/status.php HTTP/1.1" 200 96
192.168.0.185 - - [10/Sep/2016:16:14:13 +0100] "PROPFIND /remote.php/webdav/ HTTP/1.1" 404 216
192.168.0.185 - - [10/Sep/2016:16:14:18 +0100] "PROPFIND /remote.php/webdav/p/webdav/Passwords/ HTTP/1.1" 404 235
192.168.0.185 - - [10/Sep/2016:16:14:21 +0100] "PROPFIND /remote.php/webdav/p/webdav/Personal/ HTTP/1.1" 404 234

With redirect:
192.168.0.185 - - [10/Sep/2016:16:14:52 +0100] "PROPFIND /remote.php/webdav/ HTTP/1.1" 302 246
192.168.0.185 - chris [10/Sep/2016:16:14:52 +0100] "PROPFIND /owncloud/remote.php/webdav/ HTTP/1.1" 207 12168
192.168.0.185 - chris [10/Sep/2016:16:14:53 +0100] "GET /owncloud/ocs/v1.php/apps/files_sharing/api/v1/shares?path=&subfiles=true HTTP/1.1" 200 1083
192.168.0.185 - - [10/Sep/2016:16:15:14 +0100] "PROPFIND /remote.php/webdav/p/webdav/Passwords/ HTTP/1.1" 302 265
192.168.0.185 - chris [10/Sep/2016:16:15:14 +0100] "PROPFIND /owncloud/remote.php/webdav/p/webdav/Passwords/ HTTP/1.1" 404 246

ownCloud log (data/owncloud.log)

No logs generated

Tell us what could be improved:

the iOS app is attempting to connect, assuming that OC is running in the root, regardless of what the server URL is set to. It also corrupts the URL when connecting; see the extra "/p/webdav" in the webdav URLs above. This does not happen if owncloud is running in the root.

相关推荐
最新评论 (38)
nasli 2017-10-9
1

您好@pixelseventy2,
感谢您的反馈, 将检查它。

原文:

Hi @pixelseventy2,
thanks for your feedback, will check it.

guruz 2017-10-9
2

您在客户端设置中设置了哪个确切的 URL?

原文:

Which exact URL did you set in the client settings?

pixelseventy2 2017-10-9
3

我试过了:
https://owncloud/owncloud
https://owncloud/owncloud/

在设置重定向从/到/owncloud/已尝试:
https://owncloud
https://owncloud。

后者工作良好后, 我移动 OC 从/owncloud/-这个设置与/owncloud/一直在 Android 工作了多年, 仍然是, 并一直在 iOS 工作, 直到最近

原文:

I tried:
https://owncloud.p*****.net/owncloud
https://owncloud.p*****.net/owncloud/

and after setting up the redirect from / to /owncloud/ tried:
https://owncloud.p*****.net
https://owncloud.p*****.net/

The latter worked fine after I moved OC from /owncloud/ to / - This setup with the /owncloud/ has been working on Android for years and still is, and was working on iOS until very recently

nasli 2017-10-9
4

@pixelseventy2感谢您的反馈将检查它

原文:

@pixelseventy2 thanks for your feedback will check it

denisblum 2017-10-9
5

我也有同样的问题请参见单独的问题。
从我的观点来看, 这是一个问题, 从 iPhone 应用程序 Owncloud 版本 3.5.1, 而不是从 Owncloud 服务器的设置, 因为我没有收到错误信息使用 iPad 或 Safari 的桌面。

你有办法吗?

原文:

I have the same problem. See separate issue.
From my point of view, its a problem from the iPhone App Owncloud Version 3.5.1 and not from the owncloud-server settings, because i dont receive the error message by using iPad or Safari by desktop.

Do you have a solution?

denisblum 2017-10-9
6

你有什么消息要告诉我们吗?
问题/错误是否可重现?

原文:

Do you have any news for us / me?
Is the problem / error reproducible ?

denisblum 2017-10-9
7

嗨 Nasli
那问题呢?
你有好消息要告诉我们吗?
iphone 应用程序的更新是否可用?

请注意: iPad 上的应用程序工作正常!它唯一的 iphone 版本

请给我一个反馈

原文:

Hi Nasli,
What about the issue?
Do you have good news for us?
Is an update for the iphone app available?

Please note: the app on iPad works fine! Its only the iphone Version

Please give me a feedback

jesmrec 2017-10-9
8

@pixelseventy2您能否为我们提供一个测试帐户?我们不能重现错误。

原文:

@pixelseventy2 could you provide us an test account? we can not reproduce the error.

endcarnage 2017-10-9
9

@jesmrec: 我的一个朋友在我的安装上有相同的错误, 所以我可以为您提供一个测试帐户。如何向您发送访问数据?

原文:

@jesmrec: A friend of mine has the same error on my installation, so I could provide you with a test account. How should I send you the access data?

jesmrec 2017-10-9
10

@endcarnage将其发送到apps@owncloud.com apps@owncloud. com。谢谢!!!!

原文:

@endcarnage send it to apps@owncloud.com. Thank you!!!!

jesmrec 2017-10-9
11

检查您发送的服务器, 我无法重现错误。我在帐户中创建的不同文件夹中正确浏览了任何错误。

我用的是 v9.3.5 的 iPhone

问题是否可重现?

原文:

Checking the server you sent, i could not reproduce the error. I browsed correctly through different folders i created in the account with any error.

I used an iPhone with v9.3.5.

Is the problem reproducible yet?

denisblum 2017-10-9
12

我仍然有问题与 iphone 10.1。1
它似乎与 iphone < 10 的工作?

或?

原文:

I still have the Problem with iphone 10.1.1
It seem that it works with iphone < 10????

Or?

jesmrec 2017-10-9
13

@denisblum

检查与 ios 10.1.1, 我可以重现的 bug, 所以它似乎是一个与该 ios 版本的应用程序的问题。我检查了它与 iOS 9.3 一样, 在第一个消息的参考。

请不要关闭测试帐户, 如果它是您。

@nasli, 我使用以下设置重现:

iPhone 6 加
iOS v10.1.1 (14B100)
应用程序版本3.5。x

iOS 版本 9.3.x-> 不可重现

原文:

@denisblum

Checking with iOS 10.1.1, i can reproduce the bug, so it seems to be a problem related with the app in that iOS version. I checked it with iOS 9.3 like the reference in first message.

Please do not close the test account, if it is posible.

@nasli, i use the following set-up to reproduce:

iPhone 6 Plus
iOS v10.1.1 (14B100)
app versions 3.5.x

with iOS version 9.3.x -> not reproducible

jesmrec 2017-10-9
14

今天, 我用测试帐户和10.1.1 设备进行了一次检查, 但是现在的问题与最新的尝试相同的环境无法重现。

@denisblum如果问题仍然存在, 可以使用此 (或其他) 帐户进行检查吗?

原文:

today i performed a check with the test account and the 10.1.1 device, but the problem is now not reproducible with the same environment as the latest try.

@denisblum could you check with this (or another) account if the problem persists?

denisblum 2017-10-9
15

我还是有问题!
我们能做什么?

原文:

I still have the problem !
What can we do?

denisblum 2017-10-9
16

我的设备:
Iphone 6 加
10.1。1
应用程序3.5。1

仍然不工作

原文:

My device:
Iphone 6 plus
10.1.1
App 3.5.1

Still not working

jesmrec 2017-10-9
17

问题是否在您发送的同一帐户中重现?

原文:

is the problem reproducible in the same account you sent?

endcarnage 2017-10-9
18

错误发生在另一个帐户中。我们只是在这里测试它, 它只发生在其他帐户。我们比较了两个帐户, 我注意到作为一个区别, 一个帐户有一个大写的第一个字母名字和姓氏。因此, 我们改变了在测试帐户, 错误是可重现的。我们想确保它是真正的原因, 所以我们改回到旧的全名, 错误消失了。可悲的是, 再次更改为大写字母名字/姓氏错误没有再次 occurr。

所以我想让你登录到错误发生的帐户, 所以我们移动了该帐户的所有文件, 并更改了密码, 所以我们可以让你访问它, 但在那之后, 错误就消失了。当然, 无论我们做什么, 现在错误不会再次发生。

因此, 问题似乎是不能重现与我的服务器了, 我不知道, 有什么可能导致它。

原文:

The error occurred in another account. We just tested it here and it only occurred in the other account. We compared both accounts and I noticed as a difference, that one account had a capital first letter firstname and lastname. So we changed that in the test account and the error was reproducible there. We wanted to make sure it was really the cause, so we changed back to the older full name and the error was gone. Sadly after changing again to capital letter firstname/lastname the error did not occurr again.

So I wanted to let you login into the account where the error occurs, so we moved all files from that account and changed the password, so we can let you access it, but after that the error was gone. And of course whatever we do, now the error does not occur again.

So the problem seems to be not reproducible with my server anymore and I have no clue, what could possibly cause it.

denisblum 2017-10-9
19

我不知道, 如果爱懂你的权利。我不能改变现有的用户名!但它的权利, 所有帐户都有一个大写的第一个字母名字和姓氏。通过使用用户名为 "测试人员" 的新测试人员, 我仍然会收到问题!
从我的角度来看, 我们没有一个用户名的问题, 因为每个人都可以登录。选择/打开文件夹时出现错误。另一点是, 该应用程序运行完美的使用 iphone 5 与 < v10 和 iPad 或其他设备。

也许下面的观点会帮助你解决问题:
似乎 iPhone > v10 的用户可以登录, 但文件夹结构是旧的!结构不会刷新。通过选择文件夹或 manualy 刷新文件夹视图, 错误就来了。

原文:

I dont know, if oi undestand you right. I cant change existing usernames!?? But its right, all accounts have a capital first letter firstname and lastname. by using a new Test user with Username "tester", i still receive the problem!
From my point of view, we do not have a problem with usernames, because everybody are able to login. The error came by choosing / open a folder. Another point is, that the app runs perfect by using iphone 5 with <v10 and with iPad or other devices.

Perhaps the following point will help you to fin the problem:
it seems that users with iPhone >v10 are able to login but the folder structure are old! the structure will not refresh. by choosing a folder or by manualy refresh the folder view the error is coming.

denisblum 2017-10-9
20

另一点:
一切都很好, 如果我使用云在每个设备上使用 safari!
这似乎是问题是应用程序

原文:

Another point:
everything is fine, if i use the cloud by using safari on every device !
it seems thats the problem is the app

jesmrec 2017-10-9
21

@denisblum@endcarnage您从以后的版本升级了吗?还是从苹果专卖店里装的?
您是否从 ios 9 升级到 ios 10, 并安装了相同的应用程序版本?

了解在特定的升级方案中是否发生了问题会很有用。

原文:

@denisblum @endcarnage did you upgrade the version from a later one? or installed it from apple store?
did you upgrade from iOS 9 to iOS 10 with the same app version installed?

it can be useful to know if the problem happened in a particular scenario of upgrading.

endcarnage 2017-10-9
22

@denisblum 我没有改变用户名, 但在 webinterface 至少管理员有选项来指定用户的真实姓名。更改服务器上的真实名称不久会导致该错误, 但不能重现。

同时, 使用 webinterface 删除服务器上受影响用户的所有文件, 确实删除了该用户的错误。

@jesmrec我已经把这个问题转达给我的朋友。我自己没有一个苹果设备和错误发生在我的朋友的设备。他已经安装了商店的应用程序, 并说他没有安装任何更新, 但我确实更新了服务器上的 owncloud 版本。

原文:

@denisblum I did not change the username, but on the webinterface at least the Adminstrator has the option to specify real names of the user. Changing that real name on the server did shortly cause that error, but not reproducible.

Also deleting all files of the affected user on the server using the webinterface, did remove the error for that user.

@jesmrec I have forwarded that question to my frined. I myself don't have an apple device and the error occurred on the device of my friend. He has installed the app from the appstore and says that he did not install any updates, but I did update the version of owncloud on the server.

jesmrec 2017-10-9
23

@endcarnage您的朋友的任何反馈?

原文:

@endcarnage any feedback from your friend?

endcarnage 2017-10-9
24

他已经安装了商店的应用程序, 并说他没有安装任何更新, 但我确实更新了服务器上的 owncloud 版本。

这是他的反馈。

原文:

He has installed the app from the appstore and says that he did not install any updates, but I did update the version of owncloud on the server.

That was his feedback.

nasli 2017-10-9
25

@endcarnage是否已尝试删除应用程序内的用户帐户并再次添加它?这可以是在应用程序设置视图的性能

但是我在服务器上更新了 owncloud 的版本。

您在服务器中的更新是什么?
升级服务器版本?在这种情况下, 从巫婆版本。
更改服务器上的端点?也许更路径?
添加了某种重定向?

Tahnk 您的反馈调试此问题

原文:

@endcarnage have you tried to remove user account inside the app and added it again? This can be performance on the app settings view

but I did update the version of owncloud on the server.

Which was the update in the server that you did?
upgrade server version? In that case from witch version.
change endpoint on the server? Maybe more subpaths?
added some kind of redirection?

Tahnk you for your feedback debugging this issue

davivel 2017-10-9
26

@endcarnage , @denisblum , 请从服务器提供日志;在 iOS 应用程序中复制 bug 后, 将其正确地进行。

@pixelseventy2 , 这对您来说仍然是个问题吗?

谢谢

原文:

@endcarnage , @denisblum , please, provide logs from the server; take them right after reproducing the bug in the iOS app.

@pixelseventy2 , is this still an issue for you?

Thanks

endcarnage 2017-10-9
27

@daviel错误 ist 不再重现我, 但错误应该在存档日志的这一部分: http://pastebin.com/LVrdXj7N (access.log 和 error.log)
重要的 web 服务器设置有:
DocumentRoot/无功/万用/克莱恩
别名/owncloud "/var/www/owncloud/"

@nasli我想我朋友的消息是错的, 对不起。我只是搜索我的信使档案, 并可以重建以下一连串的事件:

  • 他报告说, 该应用程序已经不再工作 (我相信在安装应用程序更新后)
  • 我试图找出, 什么是错误的, 并发现我没有安装最新版本的 owncloud, 因为 owncloud 移动到另一个存储库, 我从旧的安装
  • 我假设应用程序中的错误是由最新的应用程序和旧的 owncloud-服务器软件之间的不兼容造成的
  • 我将服务器从版本8.1 更新到 9.1 (当前9.1.2 安装使用) 和新的存储库http://download.owncloud.org/download/repositories/stable/Debian_8.0/
  • 该应用程序仍然没有工作
  • 我试图给你访问帐户的错误和错误莫名其妙地解决
原文:

@daviel The error ist not reproducible anymore for me, but the error should be in this part of the archived logs: http://pastebin.com/LVrdXj7N (access.log and error.log)
The important webserver settings are:
DocumentRoot /var/www/kraven.my-wan
Alias /owncloud "/var/www/owncloud/"

@nasli I think the information from my friend was wrong, sorry for that. I just searched through my messenger archive and can reconstruct the following chain of events:

  • He reported the app isn't working anymore (i presume after installing an update of the app)
  • I tried to figure out, what was wrong and found out I did not have the latest version of owncloud installed, because owncloud moved to another repository and I had it installed from the old one
  • I assumed the error in the app was caused by an incompatibility between newest app and old owncloud-server-software
  • I updated the server from version 8.1 to 9.1 (currently 9.1.2 is installed using the ) and to the new repository http://download.owncloud.org/download/repositories/stable/Debian_8.0/
  • The app did still not work
  • I tried to give you access to the account with the error and the error was somehow solved
pixelseventy2 2017-10-9
28

这对我来说不是一个问题, 因为我能够改变我的实例, 以运行在网站的根, 而不是在 owncloud 文件夹

原文:

It's not been an issue for me for a while, as I was able to change my instance to run at the root of the site, not under the /owncloud folder

kuking 2017-10-9
29

嗨, 我想我有同样的错误:

  • 我可以看到文件和文件夹的列表, 一旦我打开应用程序, 即 "Folder1, Folder2, 我. jpg"
  • 点击图像 me.jpg , 收到以下错误信息:

此时无法连接到服务器。

  • 以下内容将显示在 access.log :

[...] "PROPFIND /remote.php/webdav/ebdav/me.jpg HTTP/1.1" 405 166 "-" "Mozilla/5.0 (iOS) ownCloud-iOS/3.5.1"

  • 点击文件夹 "文档", 我会收到以下错误信息:

无法创建文件夹。

  • 以下内容将显示在 access.log :

[...] "PROPFIND /remote.php/webdav/ebdav/Documents/ HTTP/1.1" 405 166 "-" "Mozilla/5.0 (iOS) ownCloud-iOS/3.5.1"

请注意可疑的 "ebdav/" 在 url 中, 它感觉就像一个字符串操作出错了;最后: 我的 ownCloud 安装在 /cloud 路径前缀中。它与 ebdav/ 的字符数量完全相同 (6)。OP 在他的 url 中复制了 "p/webdav/" 前缀。对我来说够可疑的 --谢谢!

原文:

Hi, I think I have the same error:

  • I can see the list of files and folders as soon as I open the app i.e. "Folder1, Folder2, me.jpg"
  • tapping on the image me.jpg, I get the following error message:

It is not possible to connect to the server at this time.

  • The following appears in the access.log:

[...] "PROPFIND /remote.php/webdav/ebdav/me.jpg HTTP/1.1" 405 166 "-" "Mozilla/5.0 (iOS) ownCloud-iOS/3.5.1"

  • tapping on a folder "Documents", I get the following error message:

Folder could not be created.

  • The following appears in the access.log:

[...] "PROPFIND /remote.php/webdav/ebdav/Documents/ HTTP/1.1" 405 166 "-" "Mozilla/5.0 (iOS) ownCloud-iOS/3.5.1"

Please notice the suspicious "ebdav/" in the URLs, It feels like a string manipulation gone wrong; Finally: My ownCloud is installed in a /cloud path prefix. Which has exactly the same amount of characters (6) as ebdav/. The OP has duplicated "p/webdav/" prefixes in his URLs. Suspicious enough for me. --Thanks!

ggdiez 2017-10-9
30

您好@kuking

我同意你的观点也许在动态创建 url 的方法中发生了一些错误。我需要使用您的服务器在调试模式下检查它。

您能否为我们提供您的服务器的测试用户? 将其发送到apps@owncloud.com apps@owncloud. com

谢谢,

原文:

Hi @kuking

I agree with you perhaps something is going wrong in the method that create the url dynamically. I need to check it in the debug mode with your server.

Can you provide us a test user of your server? Send it to apps@owncloud.com

Thanks,

jesmrec 2017-10-9
31

@pixelseventy2@denisblum@endcarnage@kuking

您能检查一下最新版本3.5.3 解决问题吗?

原文:

@pixelseventy2 @denisblum @endcarnage @kuking

could you check if the latest release 3.5.3 fix the problem?

kuking 2017-10-9
32

对不起, 这不是固定在3.5.3。我仍然得到错误 "文件夹无法创建"。
(但它一直在我的 ipad 上工作, 只有 iphone 失灵了。

原文:

I'm sorry but it is not fixed in 3.5.3. I'm still getting the error "Folder could not be created".
(but it has always worked on my ipad, only the iphone fails.)

jesmrec 2017-10-9
33

确定@kuking我试过你寄给我们的测试帐户, 似乎不起作用。我们应该继续研究这个问题, 测试帐户将帮助我们。

原文:

ok @kuking i tried with the test account you sent us and seems not to work. We should keep on researching on that issue and the test account would help us.

kuking 2017-10-9
34

我很抱歉, 但我没有提供一个测试帐户 (可能是别人), 我想做, 但它不能在我所处理的组织。抱歉.:(

原文:

I'm sorry but I haven't provided a test account (maybe somebody else?), I would like to do it but it can't be done in the organisation i'm dealing with. Sorry. :(

jesmrec 2017-10-9
35

我有一个测试帐户, 我虽然你发送它。我已经审阅了整个线程, 我注意到@endcarnage做到了这一点。

原文:

i have a test account and i though you sent it. I have review the whole thread and i noticed that @endcarnage did it.

davivel 2017-10-9
36

@kuking, 您在您的帐户中输入了什么 URL?是否在其中包含 /cloud 路径?

您是否可以删除该设备中的帐户并再次创建它?如果您的服务器是以某种方式重定向的, 则可能是错误地将 URL 存储在以前的版本中, 并且即使在升级到3.5.3 之后仍然会出错。

原文:

@kuking, what URL did you enter in your account? Did you include the /cloud path in it?

Is it feasible for you to delete the account in the device and create it again? If your server is redirected in some way, there is a chance that the URL was wrongly stored in a previous version and that the error persists even after upgrading to 3.5.3.

kuking 2017-10-9
37

@davivel您好, 已尝试重新创建该帐户, 它现在可以正常工作了!谢谢!
对不起, 我没空接电话。

原文:

@davivel hi, tried by re-creating the account and it works now! Thanks!
Apologies for the delay in answering, I was not available.

nasli 2017-10-9
38

感谢更新@kuking !

@denisblum, 对您来说仍然是一个问题吗?在这种情况下, 请重新打开它, 谢谢!

原文:

Thanks for the update @kuking !!

@denisblum, is it still an issue for you? In that case, please reopen it, thanks!!

返回
发表文章
pixelseventy2
文章数
1
评论数
2
注册排名
60644