Yes, using cookies. That is the only thing I can think of as well, but can't find any issue in the client and it works ok straight after.
Here's what I see in the log (note the 401) [Tue, 17 Jul 2012 13:32:07 GMT] [info] [<0.3985.117>] 127.0.0.1 - - POST /_session 200 [Tue, 17 Jul 2012 13:32:07 GMT] [info] [<0.3985.117>] 127.0.0.1 - - GET /acme/TEMP__demofile2_1.0 404 [Tue, 17 Jul 2012 13:32:07 GMT] [info] [<0.3985.117>] 127.0.0.1 - - GET /acme/_design/TEMP__demofile2_1.0 404 [Tue, 17 Jul 2012 13:32:07 GMT] [info] [<0.3985.117>] 127.0.0.1 - - PUT /acme/_design/TEMP__demofile2_1.0 401 [Tue, 17 Jul 2012 13:32:12 GMT] [info] [<0.3985.117>] 127.0.0.1 - - POST /_session 200 [Tue, 17 Jul 2012 13:32:12 GMT] [info] [<0.3985.117>] 127.0.0.1 - - GET /acme/TEMP__demofile3_1.0 404 [Tue, 17 Jul 2012 13:32:12 GMT] [info] [<0.3985.117>] 127.0.0.1 - - GET /acme/_design/TEMP__demofile3_1.0 404 [Tue, 17 Jul 2012 13:32:12 GMT] [info] [<0.3985.117>] 127.0.0.1 - - PUT /acme/_design/TEMP__demofile3_1.0 201 and here it is working ok the next day on the same file [Wed, 18 Jul 2012 10:50:03 GMT] [info] [<0.8761.138>] 127.0.0.1 - - POST /_session 200 [Wed, 18 Jul 2012 10:50:03 GMT] [info] [<0.8761.138>] 127.0.0.1 - - GET /acme/TEMP__demofile2_1.0 404 [Wed, 18 Jul 2012 10:50:03 GMT] [info] [<0.8761.138>] 127.0.0.1 - - GET /acme/TEMP__demofile2_1.0 404 [Wed, 18 Jul 2012 10:50:03 GMT] [info] [<0.8761.138>] 127.0.0.1 - - GET /acme/_design/TEMP__demofile2_1.0 404 [Wed, 18 Jul 2012 10:50:03 GMT] [info] [<0.8761.138>] 127.0.0.1 - - PUT /acme/_design/TEMP__demofile2_1.0 201 Cheers Ian > On 20 July 2012 12:00, Ian Cox <[email protected]> wrote: >> Hi, >> >> I have been using couchdb for a short while, hopefully going live with >> our project later in the year. >> I have one issue which I can seem to work out. >> I have a process that submits documents to couchdb plus design documents. >> Once in a while a certain design document will fail to submit with >> {"error":"unauthorized","reason":"You are not a db or server admin."} >> The same design document worked before, and works again after this >> problem though I do seem to get this error message for a short while, >> I am not sure what makes it go away. >> >> I wondered if it was cookie related, and possibly an issue with my >> client (LoveSeat) but everything looks ok. >> I am not using any validation functions. >> >> Any idea what might else cause this sporadic behaviour? >> >> Many thanks >> >> Ian Cox > > Without any details (e.g. information from the log file), is it possible that > your authentication is cookie based and that your session has timed out? > > Likely depends on how the auth is handled within the client. > > A+ > Dave > >
