-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to download certain filetypes #342
Comments
I noticed that if I add the user to a group with higher permissions, s3Auth now displays an autogenerated page that makes it seem that s3auth sees excel files as a directory, not an file. This is what I see after clicking on the link to an excel file: This is page is auto-generated by s3auth.com. The prefix is: projects/2016/xxxxxxxx.xlsx/ |
@bobweston are you sure that that |
It most definite;y was not a directory. I uploaded the Excel file myself. I've found an alternative solution to what we were trying to use this for though. I appreciate your attempting to help. |
@bobweston I'm sorry this bug is still not fixed. We didn't have enough funds/time to work on the project. However, recently we received some donations from our grateful users and will continue to fix issues and introduce new features. Would be great if you can also donate -- to help us move forward faster. Here is the link: https://www.0crat.com/contrib/C3RP1J1CH |
I'm trying to distribute files to some folks using S3auth. (I own the rights to the files, by the way). If the file is in zip format, it works as expected. But it won't prompt to download doc, docx and excel files.
edit: It looked like you folks had fixed it for a brief time yesterday. But it is now no longer working again.
Is this an expected behavior? Can that be changed?
I'm currently able to just link to those files in my s3 bucket and users are prompted to download them. But once I put s3auth in front of the bucket, I get a java.io exception.
I love the app/service and appreciate your feedback.
The error I am seeing is (in part) below:
The text was updated successfully, but these errors were encountered: