You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Robert Newson (JIRA)" <ji...@apache.org> on 2013/02/24 21:40:13 UTC
[jira] [Resolved] (COUCHDB-1651) Server responds 400 "Exceeded
rewrite recursion limit" indefinitely
[ https://issues.apache.org/jira/browse/COUCHDB-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Newson resolved COUCHDB-1651.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.2
1.3
> Server responds 400 "Exceeded rewrite recursion limit" indefinitely
> -------------------------------------------------------------------
>
> Key: COUCHDB-1651
> URL: https://issues.apache.org/jira/browse/COUCHDB-1651
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Reporter: Paul Frazee
> Fix For: 1.3, 1.2.2
>
> Attachments: resolve_spurious_rewrite_limit_errors.patch
>
>
> Running 1.2.1 on Windows 7 as a service.
> hosts file includes "127.0.0.1 grimwire.local"
> CouchDB conf includes vhosts entries:
> grimwire.local:5984 /grimwire/_design/grimwire/_rewrite
> grimwire.local:5984/local /grimwire/_design/local/_rewrite
> 'grimwire' design doc rewrites:
> [
> {
> "from": "",
> "to": "index.html",
> "method": "GET"
> },
> {
> "from": "*",
> "to": "*"
> }
> ]
> 'local' design doc rewrites:
> [
> {
> "from":"",
> "to":"index.html",
> "method":"GET"
> },
> {
> "from":"/posts",
> "to":"_list/wallpost/wallpost-by-created_at",
> "method":"GET"
> },
> {
> "from":"/posts",
> "to":"_update/wallpost",
> "method":"POST"
> },
> {
> "from":"/posts/:id",
> "to":"_show/wallpost/:id",
> "method":"GET"
> },
> {
> "from":"/posts/:id",
> "to":"_update/wallpost/:id",
> "method":"PUT"
> },
> {
> "from":"*",
> "to":"*"
> }
> ]
> Problem:
> The requests work as expected for some unknown period, then begin to respond with a 400 status and the "Exceeded rewrite recursion limit" error message. Changing the rewrites rules for both applications, including setting them to empty arrays, had no effect.
> The problem was solved by restarting the CouchDB service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira