aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Lu <chrislusf@users.noreply.github.com>2018-09-27 01:13:22 -0700
committerGitHub <noreply@github.com>2018-09-27 01:13:22 -0700
commitb5f3578fe4847237042cb21244c01aa42b8eed38 (patch)
tree75532cdfe1f1a2bb6da52d8ee69524bcf3200391
parent83ab3966d1e08b9c35c6d9fb15425d5e0766d46e (diff)
downloadseaweedfs-b5f3578fe4847237042cb21244c01aa42b8eed38.tar.xz
seaweedfs-b5f3578fe4847237042cb21244c01aa42b8eed38.zip
Update README.md
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index eb6463eb5..1da5158da 100644
--- a/README.md
+++ b/README.md
@@ -110,7 +110,7 @@ SeaweedFS uses HTTP REST operations to write, read, delete. The responses are in
To upload a file: first, send a HTTP POST, PUT, or GET request to `/dir/assign` to get an `fid` and a volume server url:
```
-> curl -X POST http://localhost:9333/dir/assign
+> curl http://localhost:9333/dir/assign
{"count":1,"fid":"3,01637037d6","url":"127.0.0.1:8080","publicUrl":"localhost:8080"}
```
@@ -186,7 +186,7 @@ http://localhost:8080/3/01637037d6.jpg?height=200&width=200&mode=fill
SeaweedFS applies the replication strategy at a volume level. So, when you are getting a file id, you can specify the replication strategy. For example:
```
-curl -X POST http://localhost:9333/dir/assign?replication=001
+curl http://localhost:9333/dir/assign?replication=001
```
The replication parameter options are: