You need to figure out a way to get the HTTP that get's send. There is, in all cases on our side, and in all cases i researched on the java side (server), a high statistically propabillity (99, 9999% ) that what you are sending is wrong, most likely wrongfully encoded, or just some random character in front of the XML.
Frank Mantek Google On Feb 27, 10:18 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > The message body is created by Javascript (broadvision customized > server side javascript). Yes, it is creating xml. If you can send me > the logs if at all you have any access to, it wud b gr8!! > > Thanks > Venkata nanduri > > On Feb 24, 10:57 am, "Frank Mantek" <[EMAIL PROTECTED]> wrote: > > > ok... what's the server infrastrucure? I am not familiar with "Broadvision" > > (what you mentioned above). What language is creating the request body > > (creates the xml?) ? > > > Frank Mantek > > Google > > > On 2/23/07, KoolGuy <[EMAIL PROTECTED]> wrote: > > > > I am sending this request from the server. So, I have no clue of how > > > to obtain the trace for a request made from server. > > > > On Feb 23, 4:52 pm, "Frank Mantek" <[EMAIL PROTECTED]> wrote: > > > > The problem is that this is probably not what's on the wire. I would > > > guess > > > > that if you used an http sniffer, you would see that there are some > > > bytes in > > > > front of the <?xml... that are causing the problem (I am just guessing > > > here, > > > > of course, but i did run into similar issues in the past). Can you get > > > an > > > > http trace? > > > > > Frank Mantek > > > > Google > > > > > On 2/23/07, Venkata Nanduri <[EMAIL PROTECTED]> wrote: > > > > > > For testing sake I just hard-coded the XML. And sending the entry XML > > > in > > > > > the body to the URL using Broadvision's post Method. Here's the exact > > > XML > > > > > that I printed in my logs: > > > > **************************************************************************************** > > > > > > <?xml version='1.0' encoding='UTF-8'?><entry xmlns=' > > > > >http://www.w3.org/2005/Atom'xmlns:gd='http://schemas.google.com/g/2005' > > > <http://schemas.google.com/g/2005%27>><category > > > > > scheme=' > > >http://schemas.google.com/g/2005#kind'term='http://schemas.google.com... > > > <http://schemas.google.com/g/2005#event%27>></category><title > > > > > type='text'>Tennis with Beth</title><content type='text'>Meet for a > > > quick > > > > > lesson.</content><author><name>Venkata Nanduri</name><email> > > > > > [EMAIL PROTECTED]</email></author><gd:transparency value=' > > >http://schemas.google.com/g/2005#event.opaque' > > > > > <http://schemas.google.com/g/2005#event.opaque%27 > > > >></gd:transparency><gd:eventStatus > > > > > value='http://schemas.google.com/g/2005#event.confirmed'< > > >http://schemas.google.com/g/2005#event.confirmed%27 > > > >></gd:eventStatus><gd:where > > > > > valueString='Rolling Lawn Courts'></gd:where><gd:when > > > > > startTime='2007-04-17T15:00: 00.000Z' endTime='2007-04-17T17:00: > > > 00.000Z > > > > > '></gd:when></entry> > > > > ************************************************************************************************* > > > > > > Thanks for your help.... > > > > > > On 2/23/07, Frank Mantek <[EMAIL PROTECTED]> wrote: > > > > > > > Can you send what is actually on the wire? "Content is not allowed > > > in > > > > > > prolog" normally indicates an encoding issue (some random/incorrect > > > UTF > > > > > > indicator, e.g.) - it really is that in the prolog of your message > > > there > > > > > > is is stuff that does not belong... > > > > > > > Frank Mantek > > > > > > Google > > > > > > > On 2/23/07, Venkata Nanduri < [EMAIL PROTECTED]> wrote: > > > > > > > > Thanks... this seems to be working thought it gave me a redirect > > > > > > > URL... I am still working on getting it working .. as now I am > > > with the > > > > > > >error: > > > > > > > "org.xml.sax.SAXParseException: Content is not allowed in prolog." > > > > > > > > MY EVENT XML: > > > > ********************************************************************************************** > > > > > > > <entry xmlns=' > > >http://www.w3.org/2005/Atom'xmlns:gd='http://schemas.google.com/g/2005'< > > >http://www.w3.org/2005/Atom%27xmlns:gd=%27http://schemas.google.com/g... > > > >><category > > > > > > > scheme=' > > >http://schemas.google.com/g/2005#kind'term='http://schemas.google.com...< > > >http://schemas.google.com/g/2005#kind%27term=%27http://schemas.google... > > > >></category><title > > > > > > > type='text'>Tennis with Beth</title><content type='text'>Meet for > > > a quick > > > > > > > lesson.</content><author><name>Venkata Nanduri</name><email> > > > > > > > [EMAIL PROTECTED]</email></author><gd:transparencyva > > > > > > > lue='http://schemas.google.com/g/2005#event.opaque' > > > > > > > <http://schemas.google.com/g/2005#event.opaque%27 > > > >></gd:transparency><gd:eventStatus > > > > > > > value='http://schemas.google.com/g/2005#event.confirmed' > > > > > > > <http://schemas.google.com/g/2005#event.confirmed%27> > > > > > > > ></gd:eventStatus><gd:wh > > > > > > > ere valueString='Rolling Lawn Courts'></gd:where><gd:when > > > > > > > startTime='2007-04-17T15:00:00.000Z' endTime='2007-04-17T17:00: > > > 00.000Z > > > > > > > '></gd:when></entry> > > > > ************************************************************************************************************** > > > > > > > > Thanks for your help.... > > > > > > > > On 2/23/07, Ryan Boyd (Google) < [EMAIL PROTECTED]> wrote: > > > > > > > > > Hello, > > > > > > > > > Sorry about misinterpretting your original message. However, it > > > > > > > > does look like you maybe set the scope parameter as 'http' when > > > requesting > > > > > > > > your one-time-use AuthSub token, yet you were using 'https' to > > > do the actual > > > > > > > > POST? > > > > > > > > > Cheers, > > > > > > > > > -Ryan > > > > > > > > > On 2/22/07, KoolGuy < [EMAIL PROTECTED]> wrote: > > > > > > > > > > I have already tried the secodn URL you have provided for > > > adding > > > > > > > > > an > > > > > > > > > event using POST message with the pastederror: > > > > **************************************************************************************** > > > > > > > > > > HTTP/1.0 401 Token invalid - AuthSub token has wrong scope > > > > > > > > > > WWW-Authenticate: AuthSub realm=" > > >https://www.google.com/accounts/ > > > > > > > > > AuthSubRequest" > > > > > > > > > Cache-control: private > > > > > > > > > Content-Length: 213 > > > > > > > > > Date: Fri, 23 Feb 2007 01:12:33 GMT > > > > > > > > > Content-Type: text/html > > > > > > > > > Server: GFE/1.3 > > > > > > > > > Connection: Close > > > > ********************************************************************************************* > > > > > > > > > > CONTENT AS FOLLOWS FOR URL 2: > > > > > > > > > <HEAD> > > > > > > > > > <TITLE>Token invalid - AuthSub token has wrong scope</TITLE> > > > > > > > > > </HEAD> > > > > > > > > > <BODY BGCOLOR="#FFFFFF" TEXT="#000000"> > > > > > > > > > <H1>Token invalid - AuthSub token has wrong scope</H1> > > > > > > > > > <H2>Error401</H2> > > > > > > > > > </BODY> > > > > > > > > > </HTML> > > > > ************************************************************************************** > > > > > > > > > So---- I didn't have much luck with that solution. Thanks for > > > the > > > > > > > > > > help though.... > > > > > > > > > > On Feb 22, 9:02 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED] > > > > > > > > > > wrote: > > > > > > > > > > Hello, > > > > > > > > > > > The AuthSub scope that you used for URL 1 is correct: > > > > > > > > >http://www.google.com/calendar/feeds/ > > > > > > > > > > > However, to add an event, you must do a POST to the > > > following > > > > > > > > > URL:http://www.google.com/calendar/feeds/default/private/full< > > >http://www.google.com/calendar/feeds/ > > > > > > > > > > > I believe this should solve theerroryou're experiencing. > > > > > > > > > > > Happy coding, > > > > > > > > > > > -Ryan > > > > > > > > > > > On 2/22/07, KoolGuy <[EMAIL PROTECTED] > wrote: > > > > > > > > > > > > Hi > > > > > > > > > > > > I had to use the "Google Calendar Feeds - add an > > > event" to > > > > > > > > > simulate a > > > > > > > > > > > prototype for my company stuff. > > > > > > > > > > > Step 1: Obtained a One-Time token using the following URL: > > > > > > > > > > > > https%3a%2f%2fmcfl1u5v.MYCOMPANY.com%3a1443%2fcgi-bin > > > > > > > > > > > %2fim0drxc3%2fconsu > > > > > > > > > > > mer%2fcBLAHBLAHBLAH%3dLftNavOtcTmpl%26LeftNavHighlight > > > > %3dNavPdpDownloadForm%26MarcoPolo%3dY%26BV_SessionID%3d%40%40%40 > > > > > > > > > > > %401392004170.1172189622%40%40%40%40%26BV_EngineID > > > > %3dccccaddkfejdmffcejicegjdfgldfoi.0&scope=http%3a%2f%2fwww.google.com > > > > > > > > > > > %2fcalendar%2ffeeds%2f > > > > > > > > > > > > Step 2: Obtained a Session Token using this one-time token > > > > > > > > > using > > > > > > > > > > > BroadVision's HTTP Portal GET Method with Header > > > successfully: > > > > > > > > > > > > Authorization: AuthSub token="COfE286iARDikOnXBw" > > > > > > > > > > > > Step 3: Verified the Token Scope Using TokenInfo API. > > > Result: > > > > > > > > > > > > Target:mcfl1u5v.MYCOMPANY.com > > > > > > > > > > > Scope:http://www.google.com/calendar/feeds/ > > > > > > > > > > > Secure:false > > > > > > > > > > > > Step 4: Used the session token to Add an Event to my > > > calendar > > > > > > > > > with the > > > > > > > > > > > following Header: > > > > > > > > > > > > Authorization: AuthSub > > > > > > > > > > > token="COfE286iARCjt82vBg" > > > > > > > > > > > Content-Type: application/atom+xml > > > > > > > > > > > Content-Length: 714 > > > > > > > > > > > > URL: "http://www.google.com/calendar/feeds/";; I also > > > > > > > > > tried (url = > > > > > > > > > > > " > > >https://www.google.com/calendar/feeds/default/private/full";) > > > > > > > > > > > > I AM GETTING AN ERRO WITH THE FOLLOWING HEADER FOR URL 1: > > > > ******************************************************************* > > > > > > > > > > > HTTP/1.0 400 Bad Request > > > > > > > > > > > Content-Type: text/plain; charset=iso-8859-1 > > > > > > > > > > > Cache-control: private > > > > > > > > > > > Content-Length: 19 > > > > > > > > > > > Date: Fri, 23 Feb 2007 00:56:55 GMT > > > > > > > > > > > Server: GFE/1.3 > > > > > > > > > > > Connection: Keep-Alive > > > > ********************************************************************** > > > > > > > > > > > CONTENT AS FOLLOWS: > > > > > > > > > > > Invalid Request URI > > > > > > > > > > > > I AM GETTING AN > > ... > > read more » --~--~---------~--~----~------------~-------~--~----~ 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://groups.google.com/group/google-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
