Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Ok, seriously? Do you guys claim to know anything about curl/cfhttp and dare say that you can do anything with cfhttp you can do with curl?
PUT /feeds/default/media/document%3Adocument_id
GData-Version: 3.0
Authorization: <your authorization header here>
Content-Length: 73612
Content-Type: multipart/related; boundary="END_OF_PART"
Slug: test.doc
--END_OF_PART
Content-Type: application/atom+xml
<?xml version='1.0' encoding='UTF-8'?>
<entry xmlns="http://www.w3.org/2005/Atom" xmlns:gd="http://schemas.google.com/g/2005" gd:etag="BxAaTxRZAyp7ImBq">
<category scheme="http://schemas.google.com/g/2005#kind"
term="http://schemas.google.com/docs/2007#document"/>
<title>example document</title>
</entry>
--END_OF_PART
Content-Type: application/msword
... doc contents here ...
--END_OF_PART
Even something simple like the above requires you to write the xml away to the drive _just_ to get it to work with cfhttp... and this is a ridiculously staightforward request. Next if you start looking at the uploading api's and more it requires you to manually define http params on the multipart level which seems impossible to control. This kind of stuff tends to be _simple_... with cfhttp you spend hours just to get it to work by chance.
Copy link to clipboard
Copied
Wow, holy angry thread resurrection Batman!