Comment 4 for bug 1637149

Revision history for this message
Volodymyr Litovka (doka.ua) wrote : Re: [Bug 1637149] Re: proxy-server generates malformed URL on S3 request

Hi Tim,

sorry, forgotten to add output of s3curl:

*# ./s3curl.pl --id stest -- http://s30-ams.yttm.work:8080/ | xmllint
--format -*
   % Total % Received % Xferd Average Speed Time Time Time
Current
                                  Dload Upload Total Spent Left Speed
100 219 100 219 0 0 272 0 --:--:-- --:--:--
--:--:-- 272
*<?xml version="1.0" encoding="UTF-8"?>**
**<ListAllMyBucketsResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">**
** <Owner>**
** <ID>admin:admin</ID>**
** <DisplayName>admin:admin</DisplayName>**
** </Owner>**
** <Buckets/>**
**</ListAllMyBucketsResult>**
*

I tried also set 'allow_no_owner' and 's3_acl' to True, but with no
result, while there are containers and objects in object storage in
'admin' project for admin user:

# openstack container list
+------+
| Name |
+------+
| c0 |
+------+
# openstack object list c0
+----------+
| Name |
+----------+
| list.txt |
+----------+

Thank you!

On 10/27/16 7:04 PM, Tim Burke wrote:
> I'm not sure I understand; the did the client get an error? It looks
> like everything was successful:
>
> GET / HTTP/1.0 200
>
> I guess the trouble is that the proxy is logging the path that the user
> requested (in this case '/') rather than the backend path? You can have
> swift3 emit log lines for the individual subrequests using the
> force_swift_request_proxy_log config option [1]. Note that swift3
> typically spawns several subrequests for any one client request.
>
> [1] https://github.com/openstack/swift3/blob/1.11/etc/proxy-server.conf-
> sample#L110-L118
>

--
Volodymyr Litovka
   "Vision without Execution is Hallucination." -- Thomas Edison