Jira (PUP-10164) Agent incorrectly reporting corrective changes

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper commented on PUP-10164   Re: Agent incorrectly reporting corrective changes The following can be used to generate the base64 encoded md5 value: $ echo -n 'File Data' | openssl md5 -binary | base64 - DugzajWJUDvLA8eIWVDJCQ== When using that in server.rb, puppet correctly detects that the file is insync: $ bx puppet apply -e 'file {"/tmp/file_from_server": source => "http://localhost:5678/file"}' --http_debug Notice: Compiled catalog for ... in environment production in 0.02 seconds opening connection to localhost:5678... opened <- "HEAD /file HTTP/1.1\r\nAccept: */*\r\nUser-Agent: Puppet/6.12.0 Ruby/2.3.8-p459 (x86_64-darwin18)\r\nAccept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3\r\nHost: localhost:5678\r\nConnection: close\r\n\r\n" -> "HTTP/1.1 200\r\n" -> "Content-Type: text/html\r\n" -> "Content-MD5: DugzajWJUDvLA8eIWVDJCQ==\r\n" -> "\r\n" Conn close Notice: Applied catalog in 0.04 seconds So I think we can either close this or update documentation to make it clear the Content-MD5 header needs to be the base64 encoded value. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338108.1575582719000.5994.1576127220375%40Atlassian.JIRA.