Merge pull request #48 from Financial-Times/hashed-assets-rename

Specify ContentType for hashed assets - hopefully fixes #47

tasks/deploy-hashed-assets-s3.js

@@ -22,6 +22,7 @@ function hashAndUpload(opts) {
 	var app = opts.app;
 	var bucket = 'ft-next-hashed-assets-prod';
 	var key = 'hashed-assets/' + app + '/' + file.hashedName;
+	var extension = (/\.([^.]+)$/.exec(file.name) || [undefined, undefined])[1];
 
 	return new Promise(function(resolve, reject) {
 		var s3bucket = new aws.S3({ params: { Bucket: bucket } });
@@ -33,6 +34,14 @@ function hashAndUpload(opts) {
 			// @arjun, did you think this was in milliseconds?  It's fine to set a cache header of 19.165 years but seems like an odd choice
 			CacheControl: 'public, max-age=604800000'
 		};
+		switch(extension) {
+			case 'js':
+				params.ContentType = 'text/javascript';
+				break;
+			case 'css':
+				params.ContentType = 'text/css';
+				break;
+		}
 		s3bucket.upload(params, function(err, data) {
 			if (err) {
 				console.log("Error uploading data: ", err);