harrisj / es-amazon-s3-river Goto Github PK

The issue seems to be something in the XML returned from Amazon. Basically, Amazon allows more characters in names than are allowed in the XML 1.0 format returned by S3's list objects command. This is fixed by adding a withEncoding("url") to the list objects request, with a corresponding method to unescape URLs before displaying them.

There is a weird issue where I am getting a 404 when trying to retrieve a file with spaces in the name. The issue seems to be something with decoding the URL I requested to be encoded in the river.