wapi: test that we return 200 or 201 as appropriate #318

New Issue

Open

opened 2008-02-26 16:41:36 +00:00 by zooko · 3 comments

zooko commented

2008-02-26 16:41:36 +00:00

Per source:docs/webapi.txt, web servers ought to return 200 (OK) when modifying an existing file and 201 (Created) when creating a new file. Fix ours to do that.

Per source:docs/webapi.txt, web servers ought to return 200 (OK) when modifying an existing file and 201 (Created) when creating a new file. Fix ours to do that.

zooko added the

labels 2008-02-26 16:41:36 +00:00

zooko added this to the 0.8.0 (Allmydata 3.0 Beta) milestone 2008-02-26 16:41:36 +00:00

zooko added

and removed

labels 2008-02-26 16:41:50 +00:00

zooko modified the milestone from 0.8.0 (Allmydata 3.0 Beta) to undecided

2008-02-26 16:41:50 +00:00

zooko added

code-frontend-web

and removed

labels 2008-02-26 16:41:59 +00:00

zooko commented

2008-02-26 16:42:45 +00:00

Author

webapi.txt said: " According to the

HTTP/1.1 specification (rfc2616), this should return a 200 (OK) code when
modifying an existing file, and a 201 (Created) code when creating a new
file. (TODO: as of 0.8, the web server only returns 200, never 201)."

webapi.txt said: " According to the > HTTP/1.1 specification (rfc2616), this should return a 200 (OK) code when > modifying an existing file, and a 201 (Created) code when creating a new > file. (TODO: as of 0.8, the web server only returns 200, never 201)."

warner commented

2008-06-16 20:06:11 +00:00

I think this might be implemented now (source:src/allmydata/web/filenode.py#L49), but we don't have test cases to prove it.

I think this might be implemented now (source:src/allmydata/web/filenode.py#L49), but we don't have test cases to prove it.

warner commented

2008-06-16 20:06:58 +00:00

let's pull this into the 1.2.0 milestone (the current task is to add test coverage)

let's pull this into the 1.2.0 milestone (the current task is to add test coverage)

warner modified the milestone from eventually to 1.2.0

2008-06-16 20:06:58 +00:00

zooko modified the milestone from 1.5.0 to eventually

2009-06-30 17:51:14 +00:00

tahoe-lafs modified the milestone from eventually to 1.7.0

2010-02-27 08:39:25 +00:00

tahoe-lafs added

and removed

labels 2010-02-27 08:39:50 +00:00

tahoe-lafs changed title from ~~wapi: return 200 or 201 as appropriate~~ to wapi: test that we return 200 or 201 as appropriate

2010-02-27 08:39:50 +00:00

zooko modified the milestone from 1.7.0 to soon

2010-05-30 21:35:26 +00:00

Sign in to join this conversation.

No Label

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#318

No description provided.