awkward copy request logs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
so this request:
curl -H 'x-auth-token: xxx' http://
got logged as:
Oct 14 18:36:08 saio proxy-server: 127.0.0.1 127.0.0.1 14/Oct/
I think this is wrong for two reasons:
1) I didn't copy /v1/AUTH_
2) I didn't 'x-copy-from: /test/test', I 'destination: test/monkies'
I think we should either, log the request as delivered copy (copy /test/test destination test/monkies) - or probably better/easier log the request as processed (put test/monkies x-copy-from test/test).
I think at one time we decided that we should only log GET/HEAD/PUT/POST and the COPY verb was to be logged as PUT with x-copy-from as it's processed - but maybe with the double proxy-logging middleware we missed a place where we need to straighten out the method? Similar to what happend in #1025433?
Changed in swift: | |
assignee: | nobody → Victor Feitosa (victor-feitosa) |
I think you're misreading your log message. Please try to copy again and check your log once again. My log in latest master prompts the following:
HTTP/1.1 201 Created From-Last- Modified: Wed, 11 Feb 2015 17:15:37 GMT 7c6cef941dcf0de 1f Meta-Orig- Filename: testfile From-Account: testaccount be5863bc- 0054dba8af
Content-Length: 0
X-Copied-
X-Copied-From: container1/testfile
Last-Modified: Wed, 11 Feb 2015 19:08:32 GMT
Etag: b229fb388c5bd80
X-Object-
X-Copied-
Content-Type: text/html; charset=UTF-8
X-Trans-Id: tx3c5dc3501d394
Date: Wed, 11 Feb 2015 19:08:31 GMT
'X-Copied-From' is correct and the file is copied correctly. 10.102. 22.159: 8080/v1/ testaccount/ container1/ testfile -X COPY -H "X-Auth-Token: $TOKEN" -H "Destination: container2/ testfilecopie"
The command is: curl -v -i http://
I'll put this as incomplete. If you're still experience weird log messages please notify.