I know that feed supports JSON-C, but do you get better results with ATOM? If not, you could hold the blog author to account :-)
If so, maybe including "scope": "" ? might work-around a parsing bug? (I don't know if you tried that already - you didn't specify which scope and scopeType arrangements you tried) I am not familiar with JSON-C or how it is parsed and handled on the service end - it's just a guess. It does seem odd though, that you get a 302 or broken pipe after a timeout, and not a 50x or 400 response. It is difficult to fault the request itself. cheers, David. On Wed, Jul 6, 2011 at 8:48 AM, Dale the Developer <[email protected]>wrote: > I have a newly created secondary calendar that I am attempting to > update the ACLs to make it a Public Calendar. Similar to the > following link, except using JSON-C and Google API Version 2.0: > > http://gdatatips.blogspot.com/2009/12/making-calendar-public-via-acl-feed.html > > Working from JSON-C Examples here: > > http://code.google.com/apis/calendar/data/2.0/developers_guide_protocol.html#AddAcl > > The POST is being sent to the accessControlListLink URI returned when > querying a calendar feed as an owner. > > Example in CURL (AuthSub has already been used to obtain a Session > Token in the Authorization header): > $ echo '{ "data": { "scopeType": "default", "role": "read" } }' | curl > -v --sessionid --request POST -L -H "GData-Version: 2.0" -H "Content- > Type: application/json; charset=UTF-8" -H "Authorization: AuthSub > token=\"XXXXXXXXXXXXXXXXXXXXXXX\"" -H "Content-Length: 55" --data- > ascii - "https://www.google.com/calendar/feeds/xxxxxxxxxxxxxxxxxxxxxx > %40group.calendar.google.com/acl/full?alt=jsonc" > > > My return varies from "Empty reply from server" to a HTTP 302 redirect > sending me to an unavailable page ("Location: > http://www.google.com/googlecalendar/unavailable.html";). In any of > these scenarios it takes a full 5 minutes to return the request. > > Using PUT instead of POST as suggested in the Documentation returns a > "HTTP/1.1 405 Method Not Allowed". > > Per the GAcl:scope documentation, only scopeType:default should be > necessary. > http://code.google.com/apis/calendar/data/2.0/reference.html#gacl_reference > However it doesn't work with any arrangement of scope and scopeType. > > Any thoughts on why this call would be not be working as specified in > the documentation? > > -- > You received this message because you are subscribed to the Google > Groups "Google Calendar Data API" group. > To post to this group, send email to > [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://code.google.com/apis/calendar/community/forum.html > -- You received this message because you are subscribed to the Google Groups "Google Calendar Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://code.google.com/apis/calendar/community/forum.html
