Re: [S3tools-general] s3browser: "AWS authentication requires a valid Date or x-amz-date header"

[DJ M. <dj...@ya...>]

Hi Michal.

Whoops, you're onto something there.  I installed Debian's php-pear =
package because I was getting the following errors:


"Warning: require_once(PEAR.php) [function.require-once]: failed to open =
stream: No such file or directory in =
/usr/local/s3browser-1.0-beta3/s3core.php on line 3

Fatal error: require_once() [function.require]: Failed opening required =
'PEAR.php' (include_path=3D'pear:.:/usr/share/php:/usr/share/pear') in =
/usr/local/s3browser-1.0-beta3/s3core.php on line 3"


Sorry, I just assumed it was an undocumented dependency. But now that =
the package has been removed, those errors are back. Looking at =
1.0-beta1, beta2, and beta3... none of them include a file named =
PEAR.php.



Re: s3cmd.  Under Python 2.4, the program failed due to a dependency on =
elementtree.  That was apparently solved with 'apt-get install =
python-elementtree', but then it complained that 'hashlib' was missing.  =
A little research showed that hashlib is part of Python 2.5, so I =
upgraded to that release. Now it can't find elementtree again, despite =
setting PYTHONPATH to point to /usr/lib/python2.5 (which does include =
elementtree) and every subdirectory thereunder.


As you have probably guessed, I am not fluent in Python or PHP.  It =
seems that the problem lies with the supporting libraries for both s3cmd =
and s3browser, but several hours of work have not resolved this =
dependency hell.

Any pointers would be appreciated.


Thx,
DJ





-----Original Message-----
From: s3t...@li... =
[mailto:s3t...@li...] On Behalf Of =
Michal Ludvig
Sent: Wednesday, January 31, 2007 19:52
To: s3t...@li...
Subject: Re: [S3tools-general] s3browser: "AWS authentication requires a =
valid Date or x-amz-date header"

DJ Molny wrote:

> I unpacked s3browser 1.0-beta3 on my Debian / apache2 system without
> much trouble, but cant get past the s3install.php screen.  It
> consistently returns an error saying AWS authentication requires a
> valid Date or x-amz-date header.  I do not use an HTTP proxy.

Hmm that's weird. Looking at the source and at your $r dump it looks
like the x-amz-date header has been sent. Try the attached patch and see
if it helps.

And could you give s3cmd a try as well? It uses the same algorithm but
is implemented in Python and not PHP.

BTW You don't have Pear HTTP::Request and Net::URL installed anywhere
else on your system, do you?

Michal