1. 08 Jun, 2022 1 commit
    • Paul Millar's avatar
      client: add support for metalink source · c8fda5ff
      Paul Millar authored
      Motivation:
      
      FTS supports bulk operations, but using its own specific format.  The
      metalink is a well-documented (see RFC 5854) XML format that describes
      how to receive a set of files.
      
      Support for metalink would allow FTS to accept a bulk transfer request
      with the FTS user presenting the information in a standard fashion.
      
      Modification:
      
      Add initial support for parsing the metalink XML format.  The idea is
      that the user presents a base URL that all files (within the metalink
      file) are resolved against.
      
      There are several limitations with the current implementation:
      
       *  Metalink allows for a file to have multiple sources.  This patch
          selects only the best url (the one with the lowest priority value).
      
       *  There are several types of source URLs supported by metalink (http,
          bittorrent, etc.).  The code currently assumes that any source URL
          is acceptable by FTS
      
       *  In principle, the metalink allows a file to have different digest
          values, as calculated by different checksum algorithms.  Currently,
          only adler32 checksums are supported.
      
      Result:
      
      It is now possible to submit a bulk request to FTS using a metalink
      file.
      c8fda5ff
  2. 20 May, 2022 1 commit
  3. 18 May, 2022 1 commit
    • Paul Millar's avatar
      client: add support for --strict-copy flag · bfd81bc1
      Paul Millar authored
      Motivation:
      
      There are some circumstances in which it is impossible for FTS to verify
      that a transfer was successful: any attempt to do so will fail, which
      results in the overall transfer failing.
      
      Rather than failing transfers, it may be acceptable to rely on the
      result of the COPY.  If this reports success then consider the transfer
      successful.
      
      Support for this already exists in FTS.  It is only the REST client that
      is missing a flag.
      
      Modification:
      
      Add the `strict_copy` param with a default value of `False`.  Add a
      command-line argument that switches on the behaviour.
      
      Result:
      
      Someone using the REST client is now able to tell FTS that files are to
      be copied without FTS attempting to verify the success.
      bfd81bc1
  4. 16 May, 2022 3 commits
  5. 13 May, 2022 4 commits
  6. 04 May, 2022 1 commit
  7. 02 May, 2022 1 commit
  8. 28 Apr, 2022 2 commits
  9. 20 Apr, 2022 2 commits
  10. 19 Apr, 2022 3 commits
  11. 15 Apr, 2022 1 commit
    • Mihai Patrascoiu's avatar
      FTS-1775: Refactor the token validation codeflow. · eaf4c224
      Mihai Patrascoiu authored
      The _validate_token_offline() and _validate_token_online() helper function should not hide exceptions but propagate them upwards. The main validate_access_token() function takes care of the error handling and error message propagation to the client
      eaf4c224
  12. 14 Apr, 2022 6 commits
  13. 13 Apr, 2022 2 commits
  14. 11 Apr, 2022 2 commits
  15. 08 Apr, 2022 1 commit
  16. 05 Apr, 2022 1 commit
  17. 04 Apr, 2022 2 commits
  18. 03 Apr, 2022 6 commits