Subject: | Hardcoded s3 Server Name |
Hi there:
This issue is forwarded from the Debian bug tracking system, because I
think it would be more appropriate to be fixed upstream.
The bug report, from Joey Hess, was as follows:
"s3.amazonaws.com is hardcoded throughout the code. If this were moved to
a single, configurable variable, then it would be possible to use this
library to talk to a s3 compatible server such as walrus
(http://eucalyptus.cs.ucsb.edu/wiki/EucalyptusStorage_v1.4)"
Some suggested fixes could be using an environment variable to control
this sort of thing, although the most appropriate would probably be
having some key in your option hash. Incidentally, it may also be useful
to have the User Agent object (from LWP) passable as a parameter, so
that things like proxies or different LWP UserAgent subclasses can be used.
Hope this helps. If you don't consider this to be a bug, then we can fix
it downstream in Debian, but we want to keep distributions as patch-free
as possible.
Thanks in advance, and thanks for providing a useful module to the
community.
Cheers,
Jonathan