kopia lustrzana https://github.com/gaul/s3proxy
Created Tips (markdown)
rodzic
ca6c13b055
commit
51079e57cd
|
@ -0,0 +1,30 @@
|
|||
# Authentication
|
||||
|
||||
Authentication misconfiguration can cause spurious client failures. Ensure that you have NTP enabled on all machines. If all else fails you can disable s3proxy authentication via:
|
||||
|
||||
```
|
||||
s3proxy.authorization=none
|
||||
```
|
||||
|
||||
# curl debugging
|
||||
|
||||
You can use `curl` to debug s3proxy when authentication is disabled (see above):
|
||||
|
||||
* list containers in a storage account: `curl http://<proxy>/`
|
||||
* list blobs in a container: `curl http://<proxy>/<containername>`
|
||||
* add a new container: `curl -X PUT http://<proxy>/<newcontainername>`
|
||||
* add a new blob to a container: `curl -X PUT -T <filename> http://<proxy>/<containername>/<newblobname>`
|
||||
|
||||
# Logging
|
||||
|
||||
Debug logging reveals more information about requests:
|
||||
|
||||
```
|
||||
java -DLOG_LEVEL=debug -jar s3proxy.jar
|
||||
```
|
||||
|
||||
Trace logging shows the client requests and server responses:
|
||||
|
||||
```
|
||||
java -DLOG_LEVEL=trace -jar s3proxy.jar
|
||||
```
|
Ładowanie…
Reference in New Issue