hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Viswanadham (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-678) Format of Last-Modified header is invalid in HEAD Object call
Date Thu, 18 Oct 2018 03:47:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Bharat Viswanadham updated HDDS-678:
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Thank You, [~elek] for fix and [~anu] for review.

I have committed it to the trunk and ozone-0.3


> Format of Last-Modified header is invalid in HEAD Object call
> -------------------------------------------------------------
>                 Key: HDDS-678
>                 URL: https://issues.apache.org/jira/browse/HDDS-678
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>         Attachments: HDDS-678.001.patch
> As of now the HEAD object return with a Last-Modified header where the last modified
date is returned as an epoch. According to the standard it should be something like this:
"Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT" (see https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html)
> The s3a unit tests are parsing this header and expect to be in the right format.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message