Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ability to set Content-Type in config #7

Open
DoWhileGeek opened this issue Nov 29, 2015 · 2 comments
Open

Ability to set Content-Type in config #7

DoWhileGeek opened this issue Nov 29, 2015 · 2 comments

Comments

@DoWhileGeek
Copy link

The current site I'm building contains html files without the .html extention, and once you remove that, s3 slaps on a application/octet-stream.

This is basically a nice-to-have, to avoid having to jump in the console.
@DoWhileGeek
Copy link
Author

Upon closer inspection the mime library sets it the content-type to application/octet-stream. I plan on making a pull request that sets the default type to 'text/html' if a type cannot be detected. This should allow s3 to serve extentionless static html pages.

@DoWhileGeek DoWhileGeek reopened this Jan 4, 2016
@DoWhileGeek DoWhileGeek mentioned this issue Jan 4, 2016
Open
@jamestalmage
Copy link
Owner

I like this idea, but I want it implemented as stated here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DoWhileGeek @jamestalmage