Title:
Bug 80698:(Watson Migration Closure)Currently, for example, if you wish to pull a PDF down programmatically using CFHTTP and convert it to a PDF document, you must save it to disk using fileWrite(path,cfhttp
| View in TrackerStatus/Resolution/Reason: Closed/Deferred/
Reporter/Name(from Bugbase): Jared Rypka-Hauer / Jared Rypka-Hauer (Jared Rypka-Hauer)
Created: 11/16/2009
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 0
Problem:
Currently, for example, if you wish to pull a PDF down programmatically using CFHTTP and convert it to a PDF document, you must save it to disk using fileWrite(path,cfhttp.fileContent..toString()), then use fileRead() or cfpdf to create a PDF document object.That's a lot of messing around for something that could be done programmatically and instantly... especially when all the required data is available at the time of the download itself.
Method:
Result:
cfhttp should have a new attribute along the lines of convert="true|false" that will cause CF to inspect the MIME type of filecontent and, if it's a supported type, automatically convert fileContent to the appropriate type. Would work for images, PDFs, spreadsheets, etc.Additionally, adding a filetype="" attribute would allow direct conversion from HTML to another filetype, allowing direct conversion from HTML to , for example, PDF.Personally I am most concerned with having CFHTTP recognize supported MIME types and handle the conversion internally and quickly.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3040415
External Customer Info:
External Company:
External Customer Name: Jared Rypka-Hauer
External Customer Email: 08C411A143BC38A7992016B6
External Test Config: 11/16/2009
Attachments:
Comments: