Clovertech

FTP a PDF and only see blank pages

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › FTP a PDF and only see blank pages

  • Creator
    Topic
  • July 20, 2017 at 7:31 pm #55454
    Tom Patton
    Participant

      This one has me banging my head against the desk…

      I can transfer a pdf file using FTP manually on my AIX server and it is legible on the other side, but when I push it through an FTP protocol thread on the engine – you can only see blank pages.

      I have binary checked on the protocol.

      I’ve tried active, but I’m going though firewalls and a VPN tunnel and passive works, but active doesn’t…

      Any thoughts would be appreciated..

      I’m attaching my log with enable_all on…

      thank yoU!

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • July 20, 2017 at 10:17 pm #85388
        David Barr
        Participant

          You might also try setting Binary on the thread encoding properties (both inbound and outbound). This is separate from the FTP protocol ascii/binary setting.

        • July 21, 2017 at 9:58 pm #85389
          Tom Patton
          Participant

            David, thank you for your response.

            I’ve tried the binary encoding on the thread, but then I can’t get authenticated…

            I’ve forced binary by using curl option – CURLOPT_BINARYTRANSFER 1.

            And it is transferring binary, but I’m getting 80,000 extra bytes added to the file….

            The file size on AIX 7.1 (CL 6.1) is 180845 and ends up as 263058.

            Here is my verbose log snippet – does anyone see anything odd?

            * Hostname was NOT found in DNS cache

            *   Trying 999.999.999.999…

            * Connected to 999.999.999.999 (999.999.999.999) port 21 (#0)

            < 220 EFT Server Enterprise 6.5.5.2

            > USER someaccount

            < 331 Password required for someaccount.

            > PASS guessyguessy

            < 230 Login OK. Proceed.

            > PWD

            < 257 "/" is current folder.

            * Entry path is ‘/’

            > EPSV

            * Connect data stream passively

            * ftp_perform ends with SECONDARY: 0

            < 229 Entering Extended Passive Mode (|||5435|).

            * Hostname was NOT found in DNS cache

            *   Trying 999.999.999.999…

            * Connecting to 999.999.999.999 (999.999.999.999) port 5435

            * Connection failed

            * connect to 999.999.999.999 port 21 failed: Connection timed out

            * Failed to connect to 999.999.999.999 port 21: Connection timed out

            * Failed EPSV attempt. Disabling EPSV

            > PASV

            < 227 Entering Passive Mode (999,999,999,999,76,163).

            * Hostname was NOT found in DNS cache

            *   Trying 999.999.999.999…

            * Connecting to 999.999.999.999 (999.999.999.999) port 19619

            * Connected to 999.999.999.999 (999.999.999.999) port 21 (#0)

            > TYPE I

            < 200 Type set to I.

            > STOR ZZTEST6_CPOE2tom6_3032184_20170719_MQNeuroOncCons_F_19520101_F_02180_1028149_02180_1028149__H0414563.pdf

            < 150 Opening BINARY mode data connection for ZZTEST6_CPOE2tom6_3032184_20170719_MQNeuroOncCons_F_19520101_F_02180_1028149_02180_1028149__H0414563.pdf.

            * We are completely uploaded and fine

            * Remembering we are in dir “”

            < 226 Transfer complete. 263058 bytes transferred. 263058 bps.

            > QUIT

            < 221 Service closing control connection.

            * Closing connection 0

            any help is appreciated…

          • July 21, 2017 at 10:03 pm #85390
            Tom Patton
            Participant

              I should also note that AIX FTP transfers this file at the correct size and it’s able to be displayed – CURL under TCL and in a FTP protocol thread has this problem where the file can’t be displayed and the file size is not accurate.

            • July 23, 2017 at 11:36 pm #85391
              Elisha Gould
              Participant

                If you are trying to send it using tcl, you may need to convert the encoding.

                Code:

                set myData [encoding convertto identity $aData]


                I can’t remember what you need to set the thread encoding to. I think it may be passthrough or binary.

                For background cloverleaf does encoding from the default tcl encoding (utf-8) to the encoding specified in thread, then utilised as utf-8 throughout the translations. It will convert back to the correct encoding at the end, but it messes up when trying to do any translations.

                The end result is that you’ll need to convert to identity to get binary data that is useful for translation.

                My thought is that it should have been set up to go from the encoding specified to utf-8, then to whatever encoding is specified in the outbound.

            • Author
              Replies
            Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.