RFE: Allow non-SSL CLI import.

[jamoore]

There's currently no flag for the CLI or for import in particular to drop out of SSL like the checkbox in the clients.

This could likely be backported to dev_4_4, and would generally speed-up import for DropBox?, et al.

[jamoore]

This requires mostly stepping through the code to make sure that all code paths end up with a non-SSL connection for transferring binary to the server. If it's *not* currently happening, it would be better to make that the default, and then subsequently add an option to turn it off.

[jamoore]

I've looked into this (lightly) a few times, and never been able to convince myself of the state of things. Probably needs a detailed reading and a quick final decision. I don't suspect the solution (if needed) will be hard.

[jamoore]

I get:

2015-04-20 15:39:04,846 53909      [      main] WARN   ts.importer.transfers.UploadFileTransfer - b620117a-e4b7-4d78-94e1-a93d1b126177/779c3789-ea2c-44c2-ba87-0e495a243f06-RepoRawFileStoreI -t -e 1.0:tcp -h 192.168.178.23 -p 58134:tcp -h 192.168.59.3 -p 58134:tcp -h 192.168.178.96 -p 58134

from

+++ b/components/blitz/src/ome/formats/importer/transfers/UploadFileTransfer.java
@@ -47,7 +47,7 @@ public class UploadFileTransfer extends AbstractFileTransfer {
         final File file = state.getFile();
         final byte[] buf = state.getBuffer();
         final ChecksumProvider cp = state.getChecksumProvider();
-
+
         FileInputStream stream = null;

         try {
@@ -56,12 +56,13 @@ public class UploadFileTransfer extends AbstractFileTransfer {
             long offset = 0;

             state.uploadStarted();
-
+
             // "touch" the file otherwise zero-length files
+            log.warn(rawFileStore.toString());

i.e. the connection is tcp and not ssl. In other words, this is already the case. Closing.