Late to the party, but I can confirm that "Internal Error" code 500
issues can consistently be triggered by malformed input.
Sending incorrectly formatted requests often trigger an error like
this:
{"error":{"code":500,"message":"Internal Error","errors
[{"domain":"GData","code":"ServiceException","internalReason":"Internal
Error"}]}}
Tested with both ATOM and JSON-C, using curl and PHP + curl. PHP's
json_encode() is not always compatible with Google's JSON-C
formatting. Further errors of the same flavor can be encountered when
the 'GData-Version: 2.0' header is not set when sending JSON-C.
On May 19, 8:33 am, Matthew Poer <[email protected]> wrote:
> Agreed, issue exists here as well using the Zend/Gdata library. Issue is
> only present when using the non-default calendar.
--
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
