Issue 713 in gdata-python-client: gdata problem with gcalcli

141 views
Skip to first unread message

gdata-pyt...@googlecode.com

unread,
Dec 12, 2014, 8:28:12 AM12/12/14
to gdata-python-client-...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 713 by gaspare....@gmail.com: gdata problem with gcalcli
https://code.google.com/p/gdata-python-client/issues/detail?id=713

What steps will reproduce the problem?
1.Using gcalcli


What is the expected output?
It seems that gcalcli doesn't work for a problem with gdata api. Performing
any command ("list" in the example below) I get the following error.


What do you see instead?

gcalcli list
Password:
Traceback (most recent call last):
File "/usr/bin/gcalcli", line 2059, in <module>
BowChickaWowWow()
File "/usr/bin/gcalcli", line 1918, in BowChickaWowWow
customLocale=customLocale)
File "/usr/bin/gcalcli", line 515, in __init__
self.allCals = self.gcal.GetAllCalendarsFeed()
File "/usr/lib/python2.7/site-packages/gdata/calendar/service.py", line
82, in GetAllCalendarsFeed
return self.Get(uri,
converter=gdata.calendar.CalendarListFeedFromString)
File "/usr/lib/python2.7/site-packages/gdata/service.py", line 1108, in
Get
'reason': server_response.reason, 'body': result_body}
gdata.service.RequestError: {'status':
403, 'body': '<HTML>\n<HEAD>\n<TITLE>Forbidden</TITLE>\n</HEAD>\n<BODY
BGCOLOR="#FFFFFF" TEXT="#000000">\n<H1>Forbidden</H1>\n<H2>Error
403</H2>\n</BODY>\n</HTML>\n', 'reason': 'Forbidden'}


What version of the product are you using?
gdata 2.0.18


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

gdata-pyt...@googlecode.com

unread,
Dec 30, 2014, 3:29:04 PM12/30/14
to gdata-python-client-...@googlegroups.com
Updates:
Status: Invalid

Comment #1 on issue 713 by afs...@google.com: gdata problem with gcalcli
https://code.google.com/p/gdata-python-client/issues/detail?id=713

Looks like an auth issue, but I can't see how this relates to a bug in the
gdata library itself. Closing.
Reply all
Reply to author
Forward
0 new messages