Of course, that will depend on the file transport in use...

I'm gonna share my current collection for that option as an answer - feel free to contribute:)

asked 06 Oct '11, 12:17

Volker%20Barth's gravatar image

Volker Barth
accept rate: 34%

retagged 11 Oct '11, 04:16

Daz%20Liquid's gravatar image

Daz Liquid

Preface: We're running the FILE transport with our own HTTPS transfer facility (based on WinInet). The "server share" is made available to the clients via an IIS 6 web server. The following list was collected by means of a "brute force" attempt to upload files with all possible extensions.

I'm quite sure that some of these extensions are only problematic for our particular setup as they typically denote script files, others seem to be used by IIS for different reasons (which I don't claim to understand). - When using classical FTP servers, I guess the list would contain different entries. YMMV...

I just found out that ".url" is a bad extension for IIS, too - it seems to get blocked immediately by the web server - so now it's on the blacklist:

set remote file option public.invalid_extensions =
permanent link

answered 06 Oct '11, 12:28

Volker%20Barth's gravatar image

Volker Barth
accept rate: 34%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 06 Oct '11, 12:17

question was seen: 2,134 times

last updated: 11 Oct '11, 04:16