Hi Peter, seems like you are making good progress. Yes, probably the Authorization and GData-Version headers are lacking when you do an HTTP GET via the browser. There is no way to hoist these values onto the request URI that I know of - you must set the HTTP headers.
It seems like you can set the headers in Coda, but not see the XML? Or you can see the XML in your browser, but not set the headers? I'm not sure why you are wanting to see the result in a browser. If it is your tools that are limiting you, try Firefox with a plugin such as Tamper Data - https://addons.mozilla.org/en-US/firefox/addon/tamper-data/ to mess with headers before the browser actually sends the HTTP GET. Or take the time to get into cURL - http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man1/curl.1.html (recommended ... it is easy to post the full HTTP conversation to forums such as this). In any case, that stuff that Coda is showing in "preview" is just the 'text content' of the full XML. Buried behind the scenes is the <link rel="edit" href="http://etc"; /> inside an <entry/>. Your task is to take that XML, modify the <gd:cell/> element, and PUT the whole lot to http://etc You might find RFC 2616 to be challenging but interesting reading (Google for it). You should be comfortable with doing a "telnet www.mysite.com 80" and issuing the raw HTTP commands of your choice (eg. "HEAD / HTTP/1.0" and then hit "enter" twice). Refer to http://www.ehow.com/how_2248399_use-telnet-mac-os-x.html to find telnet on MacOS X. Coda's terminal might be a more convenient alternative. Hope that helps. cheers, David. On Wed, Aug 24, 2011 at 3:01 PM, peter buddemeyer < [email protected]> wrote: > hey David, made some good progress. i have my Client ID, Client Secrect, > etc... also, i have all my cell, worksheet, and spreadsheet based feeds wich > have giving me all the necessary id's. when i preview the cell based feed > code in Coda it gives me the URL bellow wich is a good sign, but when i run > it through a browser it comes up with the error Invalid request URI. i > think it has to do with the authorization headers? not sure where to apply > them in the URL... > > > https://spreadsheets.google.com/feeds/cells/tII6eDKja6rlb6Mt9MyfrHg/od6/private/full2011-08-12T11:03:42.267Z > Sheet1 fredb [email address] 3 1 101 21 > https://spreadsheets.google.com/feeds/cells/tII6eDKja6rlb6Mt9MyfrHg/od6/private/full/R1C12011-08-12T11:03:42.267Z > A1 Timestamp Timestamp > https://spreadsheets.google.com/feeds/cells/tII6eDKja6rlb6Mt9MyfrHg/od6/private/full/R1C22011-08-12T11:03:42.267Z > B1 Sample Question 1 Sample Question 1 > https://spreadsheets.google.com/feeds/cells/tII6eDKja6rlb6Mt9MyfrHg/od6/private/full/R1C32011-08-12T11:03:42.267Z > C1 Sample Question 2 Sample Question 2 > > > thanks much > > -pete > >
