Post a reply

Bug reports without an attached log file are usually useless.

Username

Subject

Message body

Font colour:

Font size:

Options

Disable BBCode in this post

Notify me when a reply is posted (registered users only)

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

Filename

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

File Comment

Options

Private file (available to author and site moderators only)

Topic review

2018-06-14 08:45

Thanks Martin, I had no idea that's how the MIME type was determined :-)

It appears that nothing was specified in the registry for .js files:

After adding a "Content Type" value it now works as expected!

Thanks again!

2018-06-14

I have MIME type text/plain configured for .js files:

[HKEY_CLASSES_ROOT\.js]

@="JSFile"

"Content Type"="text/plain"

And WinSCP correctly uses that for S3.

Check, what's your settings.

2018-06-13 08:14

Hello!

I was attempting to use WinSCP to send some files to S3 storage and noticed that the content-type for my *.js files was set to

binary/octet-stream

instead of the expected

application/javascript

(which is how Amazon's S3 web interface treats *.js files).

Is this possibly a limitation in the MIME Type API that WinSCP is using? (https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms775147(v=vs.85)#known-mime-types)

I noticed a related fix here: https://winscp.net/forum/viewtopic.php?t=25765 which is what lead me to find that API page.

I would be happy to offer more details or do some testing if this is indeed an issue within WinSCP.