Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-28522

Do not set Last-Modified header in initial stored, lazy rendition "empty" response

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.10-HF15
    • Fix Version/s: 10.10-HF21, 11.1
    • Component/s: CMIS, Renditions
    • Release Notes Summary:
      Last-Modified header is not set in the initial stored, lazy rendition "empty" response.
    • Backlog priority:
      750
    • Sprint:
      nxFG 11.1.11
    • Story Points:
      2

      Description

      Prior to the fix for NXP-27337 in Nuxeo 10.10-HF15, the initial response for a stored, lazy, Folderish rendition included the following headers and did NOT include a Last-Modified header:

      Content-Disposition: inline; filename=inprogress
      Content-Type: text/plain; empty=true
      Content-Length: 0
      

      The fix for NXP-27337 introduced a Last-Modified header into the initial response which differs from the Apache Chemistry CMIS Reference Implementation and confuses some CMIS clients.

      The pre-10.10 HF15 functionality regarding the Last-Modified response header in this scenario should be restored.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour
                  1h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.