Content-type header for JSON incorrect?

[Jos512]

I see that here in the code s3deploy sets the content-type header.

But for JSON files, the header becomes application/octet-stream in my bucket, which seems to be the basic header for arbitrary binary data from what I know. The proper header would be application/json for JSON files.

For me this is relevant because now Firefox and Chrome download the JSON file from my website each time, instead of allowing people to see the file's content. I attribute that to the inproper header.

[bep]

You can set the MIME type in your config.

[Jos512]

How? I used the approach below to set the content type, but that didn't have an effect. That made me think this option is not supported.

routes:
    - route: "^.+\\.(html|xml|js|css)$"
      gzip: true
    - route: "^.+\\.(png|jpg)$"
      gzip: false
    - route: "^.+\\.json$"
      gzip: true
      content-type: "application/json; charset=utf-8"