I saw this in the past, and the encoded data was the fact upload from the client, which for some reason is malformed/corrupted by the time it hits the master.
What version of puppet are you running? I'm guessing a 2.6 series; 2.7 moves this data to POST body rather than GET (Bug #6117 in redmine) precisely to fix this sort of thing. If this is on 2.7.x that would be troubling. -=Eric On Friday, June 29, 2012 8:26:48 AM UTC-7, Kmbu wrote: > > Maybe I'm doing something wrong, but I snooped some traffic and actually > caught a successful and a failed request, but it's all in HTTPS so not > really readable in order to compare. Any ideas? > > On Thursday, 28 June 2012 12:18:36 UTC+2, Felix.Frank wrote: >> >> Hi, >> >> On 06/28/2012 12:12 PM, Kmbu wrote: >> > But if it were a server-side issue, why would the error code be 400 >> (bad >> > request)? >> >> well, any HTTP server can issue 400 codes whenever it pleases, puppet is >> not obliged to restrict the code to broken request headers. >> >> That being said, you can of course start your debugging based on the >> thesis that puppetlabs have been paying attention and adhering to the >> rule. >> >> You could then e.g. just start wiresharking all your agent requests and >> once you trigger the error, compare the request to an unbroken one. >> >> Cheers, >> Felix >> > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/2A1aOEw_-84J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
