If you are using IIS7, take a look at its URL Rewrite capabilities. You should be able to catch an incoming pattern and pass the request off to the CF template of your choice. Cleaner than using a 404 handler.
Judah On Wed, Aug 25, 2010 at 2:49 PM, Brook Davies <cft...@logiforms.com> wrote: > > Thank you! I wonder, if I can set up a custom 404 error page to handle the > PUT operation if it posts with a specific filename instead of the location > of a CF template. I will review that further. This is enough to get me going > in the right direction, thanks! > > Brook > > -----Original Message----- > From: Judah McAuley [mailto:ju...@wiredotter.com] > Sent: August-25-10 2:06 PM > To: cf-talk > Subject: Re: HTTP PUT? > > > A PUT operation doesn't necessarily mean that they are putting a file > on your server. It is just an HTTP Verb. You can choose to respond to > it however you like. One way would be WebDAV which really would "put" > the file onto your server. Another option, which allows you more > control in your code, is to have them do a PUT operation to a url like > http://youserver.com/receiveput.cfm and then use GetHttpRequestData() > to get the content of what they sent, parse it, then do your thing. > > I have a site that has an api on it to receive JSON in the HTTP > request body from a .NET app with a PUT and it works just fine with > GetHttpRequestData(). No modifications to IIS were required as I > recall. > > Cheers, > Judah > > On Wed, Aug 25, 2010 at 1:59 PM, Brook Davies <cft...@logiforms.com> wrote: >> >> But I'm not PUTTING anything, they (echoSign) are putting the file on our >> server after its been signed via an HTTP Put. I guess my options (is this >> right?) are to: >> >> 1. Monitor the destination directory for the file they PUT there >> 2. Write some sort of a handler for PUT operations in CF to handle the > file >> and write it to disk. >> >> What do you think? I believe that IIS would need to be setup to allow CF > to >> handle a PUT operation. >> >> Brook >> >> -----Original Message----- >> From: Dave Watts [mailto:dwa...@figleaf.com] >> Sent: August-25-10 11:34 AM >> To: cf-talk >> Subject: Re: HTTP PUT? >> >> >>> I am looking at EchoSigns API, and it specified to provide a URL for a >>> callback that will receive the signed document via an HTTP PUT: >>> >>> "The url to which EchoSign will do a HTTP PUT operation with the final >>> signed PDF. HTTP authentication is supported using standard embedded >> syntax >>> - i.e. <http://username:passw...@your.server.com/path/to/file> >>> http://username:passw...@your.server.com/path/to/file."; >>> >>> How would I handle this via CF? I need to be able to update the database >>> when this file is delivered. >> >> CFHTTP supports all HTTP verbs, including PUT and DELETE. >> >> Dave Watts, CTO, Fig Leaf Software >> http://www.figleaf.com/ >> http://training.figleaf.com/ >> >> Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on >> GSA Schedule, and provides the highest caliber vendor-authorized >> instruction at our training centers, online, or onsite >> >> >> >> > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:336556 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
