[ 
https://issues.apache.org/jira/browse/TC-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124678#comment-16124678
 ] 

ASF GitHub Bot commented on TC-513:
-----------------------------------

GitHub user rob05c opened a pull request:

    https://github.com/apache/incubator-trafficcontrol/pull/798

    Add TO Go Whole-Content-SHA512 MIC header

    Adds Message Integrity Check header needed by ORT.
    
    Fixes TC-513

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rob05c/incubator-trafficcontrol 
to-gowholecontentsha512

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafficcontrol/pull/798.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #798
    
----
commit 08db3e716dd565e30fa9b34712c436d508009aa6
Author: Robert Butts <robert.o.bu...@gmail.com>
Date:   2017-08-12T19:00:55Z

    Add TO Go Whole-Content-SHA512 MIC header
    
    Adds Message Integrity Check header needed by ORT.
    
    Fixes TC-513

----


> Traffic Ops Golang must send Whole-Content-SHA512
> -------------------------------------------------
>
>                 Key: TC-513
>                 URL: https://issues.apache.org/jira/browse/TC-513
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops
>            Reporter: Robert Butts
>            Assignee: Robert Butts
>
> Once https://github.com/apache/incubator-trafficcontrol/pull/786 is merged 
> fixing TC-503, TO Golang must send a Whole-Content-SHA512 header, or ORT will 
> fail. (In fact, TO Golang fails without it, with the current MIC.)
> This is necessary for a Message Integrity Check. Previously Content-Length 
> was used, which must not be sent under certain circumstances with HTTP/1.1. 
> See pull/786 and TC-503 for more details.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to