On 2010-10-14 12:32PM, David Paleino wrote: > Seems like a couchdb bug. Huh, seems you're right! It took me a minute to find a URL on my regular couchdb (on port 5984) that required authorization, but I found a good one, and here's evidence that there's no WWW-Authentication HTTP header there either:
$ wget -S http://localhost:5984/_active_tasks -O - -q HTTP/1.0 401 Unauthorized Server: CouchDB/0.11.0 (Erlang OTP/R14B) Date: Thu, 14 Oct 2010 12:42:15 GMT Content-Type: text/plain;charset=utf-8 Content-Length: 64 Connection: Keep-Alive Cache-Control: must-revalidate $ wget -S http://secret:sec...@localhost:5984/_active_tasks -O - -q HTTP/1.0 401 Unauthorized Server: CouchDB/0.11.0 (Erlang OTP/R14B) Date: Thu, 14 Oct 2010 12:42:23 GMT Content-Type: text/plain;charset=utf-8 Content-Length: 64 Connection: Keep-Alive Cache-Control: must-revalidate $ wget --auth-no-challenge -S http://secret:sec...@localhost:5984/_active_tasks -O - -q HTTP/1.0 200 OK Server: CouchDB/0.11.0 (Erlang OTP/R14B) Date: Thu, 14 Oct 2010 12:42:40 GMT Content-Type: text/plain;charset=utf-8 Content-Length: 3 Connection: Keep-Alive Cache-Control: must-revalidate [] Note: the --auth-no-challenge flag for wget forces it to use "Basic" authentication. Note2: The "[]" at the end there is the file content from the _active_tasks url Thank you, - Jason -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
