Issue #6117 has been updated by James Turnbull. Status changed from Merged - Pending Release to Closed Target version changed from 2.7.x to 2.7.0
---------------------------------------- Bug #6117: Catalog GETs should shift to POST https://projects.puppetlabs.com/issues/6117 Author: eric sorenson Status: Closed Priority: High Assignee: Category: API Target version: 2.7.0 Affected Puppet version: Keywords: catalog REST Branch: Hi, looking at Bug #2668 after some discussion on IRC today, I thought this would be worth re-opening. Brice gzip+b64 encoded the URLs which definitely helps, but IMO it just pushes the problem out a little bit. Fact lists are always getting bigger and it'd be great not to have to worry about running into URL length limits and clean up the requests at the same time. Brice Figureau wrote: > > I don't think so, because we're GETting a catalog. To be RESTful, we should > keep using GET. > IMO this semantic correctness is way, way, way less important than doing something sane. Shifting catalog GETs over to POSTs, with the body as facts in x-www-form-urlencoded , allows arbitrary length of facts without making insane URLs. -- 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.
