Issue #4785 has been updated by Nigel Kersten. Target version changed from 2.6.x to Statler
---------------------------------------- Feature #4785: compress report submission when http_compression is enabled https://projects.puppetlabs.com/issues/4785 Author: Ben - Status: Accepted Priority: Normal Assignee: Category: reports Target version: Statler Affected Puppet version: 2.6.1 Keywords: Branch: While upgrading to 2.6.1 from 0.25.5 I implemented the http_compression option of remote WAN clients with good results. However with report enabled in the agent the PUT of the report is not compressed and quite large at times. I suggest compressing the report at the client before PUT'ing it to the server, where the server will see a compressed report and deal with it appropriately. Apparently using http compression w/ PUT requests is somewhat hit and miss which is why i suggest having the client compress the data rather than the comms. According to my nginx logs some reports are 3.5 Mb in size which on a slow WAN is a big transfer. With nginx's default 1M client body limit is seem this logged in its error log. 2010/09/16 09:20:16 [error] 7380#0: *576434 client intended to send too large body: 3584813 bytes This is overcome by increasing the nginx limit w/ client_max_body_size option. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
