Uploaded image for project: 'Fedora Repository Project'
  1. Fedora Repository Project
  2. FCREPO-2610

Properly manage ebucore:fileName property, or stop

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: Fedora 5.0.0
    • Fix Version/s: Fedora 5.0.0
    • Component/s: None
    • Labels:
      None

      Description

      It used to be the case that if a user provided a filename in a Content-Disposition header, fedora would populate a ebucore:filename property. Responses would have a Content-Disposition containing a matching filename

      FCREPO-2584 eliminated handling of Content-Disposition in requests
      https://jira.duraspace.org/browse/FCREPO-2584

      As a result, ebucore:filename is always "".

      The resolution to this ticket should remove the default population of ebucore:filename, and consider whether or not Content-Disposition should be returned in responses at all. If it is, then should it have a filename value? Is this still determined by ebucore:filename (if a user explicitly adds such a triple?)

        Attachments

          Activity

            People

            • Assignee:
              esc Esmé Cowles
              Reporter:
              birkland Aaron Birkland
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: