Skip to main content

Accessing CFHTTPPARAM Type of Body

I'm working on a project with Jason Blum and he's digging into REST web services with CFML. I'll be the first to admit that REST is something I haven't had to deal with much, so I'm glad to be learning from his research on all of this.

To make something truly RESTful, apparently you should be using a simple HTTP request's body as opposed to something like form fields when you do a post to the server. (Again, I'm a moron on all this stuff so if that's way off-base, I'm happy to learn more/be corrected.)

In CFML terms, typically you'll use CFHTTP and CFHTTPPARAM to make the call to the REST service, and use a CFHTTPPARAM type of BODY. The weird thing Jason was running into is how to get at the body content since it doesn't come through in any of the usual scopes.

Jason found a comment by Dan Switzer on a post on Mike Nimer's blog that provided the answer--you simply have to call getHttpRequestData(), which returns a struct, and the struct key CONTENT contains the body data.

Mostly blogging for my own future reference but thought others might find it helpful too.


Nice coincidence. I just learned this yesterday also. I had to create a page that will have xml posted to it. To simulate the post, I have cfhttpparam type="XML" value="#myXMLString#". The page that receives the post uses getHttpRequestData().content to get that xml file and parse it.

Some of the header info available in there can be helpful too.


Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (’lll be using Nginx ( as the web server/proxy and Gunicorn ( as the WSGI serverI used heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…