search

Ebeo / google-gdata

Automatically exported from code.google.com/p/google-gdata
0 stars 0 forks source link

Can't update a recently inserted EventEntry using OAuth #379

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run the attached app

What is the expected output? What do you see instead?
Expected: The event entry will be updated with the reminder
Received:
Error: Execution of request failed: 
http://www.google.com/calendar/feeds/default/private/full/qnehki
rg1v8hp9v9ggn2nkv9gc?xoauth_requestor_id=first.last@mydomain.com - Response 
String: <HTML>

<HEAD>
<TITLE>Unknown authorization header</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
<H1>Unknown authorization header</H1>
<H2>Error 401</H2>
</BODY>
</HTML>

What version of the product are you using? On what operating system?

I tried this with GData 1.4.0.2 and 1.5 on Windows 7

Please provide any additional information below.

Original issue reported on code.google.com by steve.wa...@gmail.com on 28 Apr 2010 at 9:59

Attachments:

GoogleCodeExporter commented 9 years ago 
will look into this

Original comment by fman...@gmail.com on 6 May 2010 at 2:38

GoogleCodeExporter commented 9 years ago 
2 legged oauth fails on UPDATE with the Authorization Header error, but works 
for
INSERT and DOWNLOAD (DocumentsService's Update, Insert and GetStream 
respectively).

Original comment by lri...@inquesttechnologies.com on 10 May 2010 at 5:03

GoogleCodeExporter commented 9 years ago 
It looks like there is a bug in the API regarding URL encoding.  After digging 
in a little, the returned entries look 
OK on the surface -- xoauth_requestor_id is present.  However, the entries 
returned back from the server aren't 
URL encoded as strictly as expected, and it appears it makes a difference in 
the .NET client library.  The "@" 
character should be encoded but isn't.

Rewriting the URI to encode the @ character seems to work OK.  But shouldn't be 
something developers need to 
do.

Original comment by sba...@google.com on 18 May 2010 at 3:34

GoogleCodeExporter commented 9 years ago 
Can you try this again with top of trunk? 

Frank Mantek

Original comment by fman...@gmail.com on 27 May 2010 at 5:55

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Update now appears to be working with OAuth. Thanks so much. However, now 
adding 
recurrence exceptions is no longer working for me. I'll have to open a new 
issue for 
this problem. Any idea what "Element must contain value for attribute 
specialized" 
error means when adding recurrence exception?

Original comment by steve.wa...@gmail.com on 6 Jun 2010 at 4:51

GoogleCodeExporter commented 9 years ago 
Thanks for testing this. See your new bug for a resolution (hopefully).

Frank

Original comment by fman...@gmail.com on 7 Jun 2010 at 2:43