command-line: whoops, put doesn't work #111

New Issue

zooko · 2007-08-17T21:32:13Z

zooko commented

2007-08-17 21:32:13 +00:00

I just noticed that the files I've been putting are coming out empty.

zooko added the

labels 2007-08-17 21:32:13 +00:00

zooko added this to the 0.5.0 milestone 2007-08-17 21:32:13 +00:00

zooko self-assigned this 2007-08-17 21:32:13 +00:00

zooko commented

2007-08-17 22:05:48 +00:00

Okay, so it turns out that our web server doesn't accept a header and body like this:

PUT /vdrive/global/my-webport-file-2 HTTP/1.1
Connection: close
Hostname: localhost

9999

and figure out that the body consists of everything that came between the header and the half-close of the connnection. Instead, it thinks that the body was of 0 length. On the other hand, this works correctly:

PUT /vdrive/global/my-webport-file-2 HTTP/1.1
Connection: close
Content-Length: 5
Hostname: localhost

9999

So for the v0.5 release, I'm just going to require that the file being uploaded is a local file and not stdin. :-(

Fixed by changeset:e997b220688e2baa. Opening a new ticket for v0.6. Note that the tahoe_put-web2ish.py script probably already does this right...

Okay, so it turns out that our web server doesn't accept a header and body like this: ``` PUT /vdrive/global/my-webport-file-2 HTTP/1.1 Connection: close Hostname: localhost 9999 ``` and figure out that the body consists of everything that came between the header and the half-close of the connnection. Instead, it thinks that the body was of 0 length. On the other hand, this works correctly: ``` PUT /vdrive/global/my-webport-file-2 HTTP/1.1 Connection: close Content-Length: 5 Hostname: localhost 9999 ``` So for the v0.5 release, I'm just going to require that the file being uploaded is a local file and not stdin. :-( Fixed by changeset:e997b220688e2baa. Opening a new ticket for v0.6. Note that the tahoe_put-web2ish.py script probably already does this right...

zooko added the

fixed

label 2007-08-17 22:05:48 +00:00

zooko closed this issue

2007-08-17 22:05:48 +00:00

Sign in to join this conversation.