CouchDB 复制在代理后面无法正常工作

发布于 2024-10-20 19:21:20 字数 2326 浏览 2 评论 0原文

注意：根据新信息进行了一些更新。旧的想法已添加为下面的评论。 注意：根据新信息（再次）进行了一些更新。旧的想法已添加为下面的注释（再次）。

我们在 Apache 反向代理后面的不同计算机上运行两个 CouchDB 实例。当尝试在两个实例之间进行复制时：（

curl -X POST http://user:pass@localhost/couchdb/_replicate -d '{ "source": "db1", "target": "http://user:[email protected]/couchdb/db1" }' --header "Content-Type: application/json"

我们开始使用curl来调试问题）

我们收到类似于以下内容的错误：

{"error":"case_clause","reason":"{error,\n    {{bad_return_value,\n         {invalid_json,\n             <<\"<!DOCTYPE HTML PUBLIC \\\"-//IETF//DTD HTML 2.0//EN\\\">\\n<html><head>\\n<title>404 Not Found</title>\\n</head><body>\\n<h1>Not Found</h1>\\n<p>The requested URL /couchdb/db1/_local/01e935dcd2193b87af34c9b449ae2e20 was not found on this server.</p>\\n<hr>\\n<address>Apache/2.2.3 (Red Hat) Server at 10.1.100.59 Port 80</address>\\n</body></html>\\n\">>}},\n     {child,undefined,\"01e935dcd2193b87af34c9b449ae2e20\",\n         {gen_server,start_link,\n             [couch_rep,\n              [\"01e935dcd2193b87af34c9b449ae2e20\",\n               {[{<<\"source\">>,<<\"db1\">>},\n                 {<<\"target\">>,\n                  <<\"http://user:[email protected]/couchdb/db1\">>}]},\n               {user_ctx,<<\"user\">>,\n                   [<<\"_admin\">>],\n                   <<\"{couch_httpd_auth, default_authentication_handler}\">>}],\n              []]},\n         temporary,1,worker,\n         [couch_rep]}}}"}

因此，经过进一步研究，apache似乎返回了此错误，而没有尝试访问CouchDB（根据日志文件）。需要明确的是，当输入以下 URL 时，

/couchdb/db1/_local/01e935dcd2193b87af34c9b449ae2e20

Apache 会将请求传递给 CouchDB 并返回 CouchDB 的 404 错误。另一方面，当复制发生时，实际传递的 URL 是

/couchdb/db1/_local%2F01e935dcd2193b87af34c9b449ae2e20

apache 确定为丢失文档的 URL，并返回自己的 404 错误，而没有将请求传递给 CouchDB。这至少给了我一些新的线索，但如果有人立即得到答案，我仍然可以使用帮助。

原文

Note: Made some updates based on new information. Old ideas have been added as comments below.
Note: Made some updates (again) based on new information. Old ideas have been added as comments below (again).

We are running two instances of CouchDB on separate computers behind Apache reverse proxies. When attempting to replicate between the two instances:

curl -X POST http://user:pass@localhost/couchdb/_replicate -d '{ "source": "db1", "target": "http://user:[email protected]/couchdb/db1" }' --header "Content-Type: application/json"

(we started using curl to debug the problem)

we receive an error similar to:

{"error":"case_clause","reason":"{error,\n    {{bad_return_value,\n         {invalid_json,\n             <<\"<!DOCTYPE HTML PUBLIC \\\"-//IETF//DTD HTML 2.0//EN\\\">\\n<html><head>\\n<title>404 Not Found</title>\\n</head><body>\\n<h1>Not Found</h1>\\n<p>The requested URL /couchdb/db1/_local/01e935dcd2193b87af34c9b449ae2e20 was not found on this server.</p>\\n<hr>\\n<address>Apache/2.2.3 (Red Hat) Server at 10.1.100.59 Port 80</address>\\n</body></html>\\n\">>}},\n     {child,undefined,\"01e935dcd2193b87af34c9b449ae2e20\",\n         {gen_server,start_link,\n             [couch_rep,\n              [\"01e935dcd2193b87af34c9b449ae2e20\",\n               {[{<<\"source\">>,<<\"db1\">>},\n                 {<<\"target\">>,\n                  <<\"http://user:[email protected]/couchdb/db1\">>}]},\n               {user_ctx,<<\"user\">>,\n                   [<<\"_admin\">>],\n                   <<\"{couch_httpd_auth, default_authentication_handler}\">>}],\n              []]},\n         temporary,1,worker,\n         [couch_rep]}}}"}

So after further research it appears that apache returns this error without attempting to access CouchDB (according to the log files). To be clear when fed the following URL

/couchdb/db1/_local/01e935dcd2193b87af34c9b449ae2e20

Apache passes the request to CouchDB and returns CouchDB's 404 error. On the other hand when replication occurs the URL actually being passed is

/couchdb/db1/_local%2F01e935dcd2193b87af34c9b449ae2e20

which apache determines is a missing document and returns its own 404 error for without ever passing the request to CouchDB. This at least gives me some new leads but I could still use help if anyone has an answer offhand.

分享到QQ

分享到微博

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

发布评论

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

心如狂蝶 2024-10-27 19:21:20

源 CouchDB (localhost) 告诉您远程 URL 无效。源接收的是 Apache httpd 代理的 file-not-found 响应，而不是 CouchDB 响应。

不幸的是，您可能需要进行一些反向代理故障排除。我的第一个猜测是源发送到目标的 Host 标头。也许这与您直接从第三个位置连接时有所不同？

最后，我想您可能知道这一点，但该路径

/couchdb/db1/_local%2F01e935dcd2193b87af34c9b449ae2e20

不是标准的 CouchDB 路径。当 CouchDB 看到请求时，它应该已删除 /couchdb，因此查询是针对名为 的数据库中名为 _local%2f... 的文档>db1。

顺便说一句，不要让代理在到达沙发之前修改路径，这一点非常重要。特别是，如果您发送 %2f，那么 CouchDB 最好接收 %2f，如果您发送 /，那么 CouchDB 最好接收 /。

The source CouchDB (localhost) is telling you that the remote URL was invalid. Instead of a CouchDB response, the source is receiving the Apache httpd proxy's file-not-found response.

Unfortunately, you may have some reverse-proxy troubleshooting to do. My first guess is the Host header the source is sending to the target. Perhaps it's different from when you connect directly from a third location?

Finally, I think you probably know this, but the path

/couchdb/db1/_local%2F01e935dcd2193b87af34c9b449ae2e20

Is not a standard CouchDB path. By the time CouchDB sees a request, it should have the /couchdb stripped, so the query is for a document called _local%2f... in the database called db1.

Incidentally, it is very important not to let the proxy modify the paths before they hit couch. In particular, if you send %2f then CouchDB had better receive %2f and if you send / then CouchDB had better receive /.

回复收藏 0 原文