Jira (PUP-10164) Agent incorrectly reporting corrective changes when base64 padding is missing from Content-MD5

13 views
Skip to first unread message

Josh Cooper (JIRA)

unread,
Dec 16, 2019, 5:37:04 PM12/16/19
to puppe...@googlegroups.com
Josh Cooper updated an issue
 
Puppet / Bug PUP-10164
Agent incorrectly reporting corrective changes when base64 padding is missing from Content-MD5
Change By: Josh Cooper
Summary: Agent incorrectly reporting corrective changes when base64 padding is missing from Content-MD5
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Josh Cooper (Jira)

unread,
May 1, 2020, 5:48:03 PM5/1/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Fix Version/s: PUP 6.16.0
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Josh Cooper (Jira)

unread,
May 1, 2020, 5:58:03 PM5/1/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Release Notes: Bug Fix
Release Notes Summary: When managing file resources with http(s) source parameters, puppet now leniently parses the Content-MD5 header according to RFC 2045. Previously it strictly parsed the header which caused interoperability problems when the base64 encoded value was not padded.

Josh Cooper (Jira)

unread,
May 1, 2020, 5:58:04 PM5/1/20
to puppe...@googlegroups.com

Josh Cooper (Jira)

unread,
May 1, 2020, 6:00:03 PM5/1/20
to puppe...@googlegroups.com

Melissa Stone (Jira)

unread,
May 6, 2020, 1:30:04 AM5/6/20
to puppe...@googlegroups.com

Claire Cadman (Jira)

unread,
May 19, 2020, 10:03:04 AM5/19/20
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages