Custom Query (8097 matches)
Results (259 - 261 of 8097)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1834 | provide reporting on directory sizes | |||
| Description |
provide reporting on directory sizes (i.e. the size of all the files in a directory and sub-directories) |
|||
| #1843 | Per-site firewall (SOCKS) settings | |||
| Description |
A single proxy/SOCKS setting is fine for if I am using it to connect to servers on the Internet, but not so for use inside complex network environments. Per site proxy settings are essential for use in any larger corporation, or supporting multi-client environments. For example, I work for an outsourcing company and to connect to client A, I need to use SOCKS server a, and to connect to client B, I need to use SOCKS server b, and so on, as we have a SOCKS server that acts as a gateway to every client network. In order to use FileZilla for this, every time I connect to a different site I have to go to the settings and manually change the firewall options. Note: This would be consistent with how products such as PuTTY work. Currently I connect to the same servers via SSH using PuTTY, and for each connection I define in PuTTY, I can set the SOCKS server (and SOCKS userid/password). In summary - please consider adding this, as the client is great other than this issue. (I read that the site manager was getting a make-over at some stage so maybe this could be part of that?) Zilch |
|||
| #1850 | Configurable location of FileZilla.xml | |||
| Description |
If you use FileZilla.xml instead of the registry to store site information the location of the file FileZilla.xml is fixed in the install dir of FileZilla. It would be nice to be able to specify a location yourself. In that way we could use a central FileZilla.xml file for all FileZilla users. So we can all use the same settings... Thanks, Simon. |
|||
