Peter,

I updated to 6.1 today and when uploading a new PDF I get and issue trying to download the same file. I see that DMX provides a direct link to S3 file and I assume that is related to this:
Enhancement: S3 storage provider now supports direct access to files, bypassing the web server. Security is maintained using S3's ability to ask for a temporary key.

The problem is I am getting this message:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>file_20121213_155641_JOSH LEDGER_akI.pdf</Key>
<RequestId>3C293C99AAA41987</RequestId>
<HostId>
So3LIFY06YsZM9VbYEHjtRFRXw1SRVTTq/bZvfG2d3+jgmMy7A6loU+Mzwnfor3T
</HostId>
</Error>

I changed back to SQL storage and do not have issues. Also note files upload prior to update do not have this issue. Any thoughts here?

I probably have the same issue. I receive the same message when I try to download a file that was uploaded to DMX after the upgrade to 6.1. Furthermore, when I try to download a file from DMX that was uploaded prior to the upgrade, I get a screen stating it is loading, but nothing is happening. It hangs.

I also note that the AWS access key is being displayed in the URL, while it is hanging.

The current state of DMX for us means that none of the documents are available.

I will appreciate a quick suggestion how to solve this issue.

Hmm. This worked in testing here, so I'm at a loss why it doesn't work for you. I'll have to make it an option. The reason for putting this in is that offloading to S3 while still streaming through the web server had people asking: can't we just download directly from S3. I found Amazon did support this in a secure way and implemented it. But this is not good news, naturally. Feel free to contact me directly and I'll see how fast I can get you a beta build of 6.1.1 to fix this and keep you going.

Peter

OK, I think I've found the issue. It's related to the spaces (or difference between the original name and the url encoded version of that) in the file name. I'll have a fix asap.

@MJ: can you confirm there were spaces in the filename? I.e. can you confirm the solution works as is, when you use a simple filename like "test.txt"?

BTW the access key is "public" according to Amazon and the way the url is constructed does not reveal any secrets. It's the secret key that should not fall into someone else's hands.

Peter

Peter,

I can confirm that most of the failing file names contained spaces. There is one exception, the document named Invoice8_12.pdf failes as well.

When I upload a file named: test1.doc, I can download it OK again, but it is now named: file_20121218_020957_Test1_kzC.

I look forward to the fix.

There also seems to be an issue now where files over 80MB will not upload to S3.

@Brandon: I'm not sure it's related. There is no limit inside DMX. We'd need to look if this persists in DMX 6.1.1.

Peter

This issue is still present with 6.1.1

spaces are no longer an issue with 6.1.2. Thank you!