incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wout Mertens <wmert...@cisco.com>
Subject Re: [user] Re: Using a proxy gives test suite errors
Date Tue, 17 Feb 2009 18:13:48 GMT
On Feb 17, 2009, at 6:30 PM, Jan Lehnardt wrote:

> On 17 Feb 2009, at 18:15, Wout Mertens wrote:
>
>> {"error":"unknown","reason":"<!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
/ 
>> test_suite_db/_design/test was not found on this server.</p>\n</ 
>> body></html>\n","line":331,"expressionBeginOffset": 
>> 11155,"expressionEndOffset":11167,"sourceId":670957024,"sourceURL":"http://localhost/_utils/script/couch.js?0.9.0

>> "}
>>
>> I can't figure out if this is just the test expecting the word-for- 
>> word error reply that CouchDB would send or if something isn't  
>> proxied properly by Apache.
>
> This is an Apache error message. CouchDB doesn't emit HTML. Check  
> your couch.log. Set the log level to debug, if needed.

Ok looking at the logs more closely I don't see why Apache returns  
404. Couchdb isn't returning 404 anywhere...

This is a normal run of that test:

[info] [<0.92.0>] 127.0.0.1 - - 'GET' /_utils/image/running.png 304
[info] [<0.92.0>] 127.0.0.1 - - 'DELETE' /test_suite_db/ 200
[info] [<0.92.0>] 127.0.0.1 - - 'PUT' /test_suite_db/ 201
[info] [<0.92.0>] 127.0.0.1 - - 'GET' /_uuids?count=105 200
[info] [<0.92.0>] 127.0.0.1 - - 'POST' /test_suite_db/_bulk_docs 201
[info] [<0.92.0>] 127.0.0.1 - - 'PUT' /test_suite_db/_design%2Ftest 201
[info] [<0.92.0>] 127.0.0.1 - - 'GET' /test_suite_db/_view/test/ 
summate 304
[info] [<0.93.0>] 127.0.0.1 - - 'GET' /test_suite_db/_view/test/ 
summate?reduce=false 304
[info] [<0.110.0>] 127.0.0.1 - - 'GET' /_utils/image/test_success.gif  
304

Here's the test when proxied:
[info] [<0.87.0>] ::1 - - 'GET' /_utils/image/running.png 304
[info] [<0.105.0>] Shutting down view group server, monitored db is  
closing.
[info] [<0.87.0>] ::1 - - 'DELETE' /test_suite_db/ 200
[info] [<0.87.0>] ::1 - - 'PUT' /test_suite_db/ 201
[info] [<0.87.0>] ::1 - - 'GET' /_uuids?count=105 200
[info] [<0.87.0>] ::1 - - 'POST' /test_suite_db/_bulk_docs 201
[info] [<0.87.0>] ::1 - - 'GET' /_utils/image/test_failure.gif 304

Looks like Apache is deciding all on its own that "PUT /test_suite_db/ 
_design%2Ftest" should get a 404. Is it caching the DELETE?

::1 - - [17/Feb/2009:19:05:55 +0100] "DELETE /test_suite_db/ HTTP/1.1"  
200 11
::1 - - [17/Feb/2009:19:05:55 +0100] "PUT /test_suite_db/ HTTP/1.1"  
201 11
::1 - - [17/Feb/2009:19:05:55 +0100] "GET /_uuids?count=105 HTTP/1.1"  
200 3686
::1 - - [17/Feb/2009:19:05:55 +0100] "POST /test_suite_db/_bulk_docs  
HTTP/1.1" 201 174
::1 - - [17/Feb/2009:19:05:55 +0100] "PUT /test_suite_db/_design 
%2Ftest HTTP/1.1" 404 224
::1 - - [17/Feb/2009:19:05:55 +0100] "GET /_utils/image/ 
test_failure.gif HTTP/1.1" 304 -

I don't know where Apache thinks it's ok to return 404. Anybody has  
any ideas?

Wout.

Mime
View raw message