I now appear to have the first suspected problem, case normalisation of cookies. Previously I sent a SID cookie, but intarweb seems to convert it to Sid, and Google refuses it. Is there any way to control this behaviour?
Cheers, Colin 2009/11/1 Colin Fleming <[email protected]> > Unbelievably enough, that was the problem. Thank you all for the help, that > would have taken me forever to figure out. > > Cheers, > Colin > > > 2009/11/1 Colin Fleming <[email protected]> > >> Good catch indeed! I'll try this when I get home. >> >> >> Thanks! >> Colin >> >> 2009/11/1 Peter Bex <[email protected]> >> >>> On Sun, Nov 01, 2009 at 03:36:42PM +0100, Jörg F. Wittenberger wrote: >>> >>> > I've got no idea what's going on here at all, but >>> > to me the second request looks wrong in any case. >>> > >>> > Shouldn't those parameter field separators be "&" and never ";" ??? >>> >>> Good catch. It's possible that Google doesn't allow ; as separator. >>> In that case, parameterize form-urlencoded-separator to "&;" or just "&". >>> >>> This parameter is for uri-common, which defaults to ";&" because >>> of the recommendation in the HTML spec to prefer ";" as separator, but >>> to also allow "&" on input. The reason is the former doesn't have to be >>> specially encoded in HTML. >>> >>> Cheers, >>> Peter >>> -- >>> http://sjamaan.ath.cx >>> -- >>> "The process of preparing programs for a digital computer >>> is especially attractive, not only because it can be economically >>> and scientifically rewarding, but also because it can be an aesthetic >>> experience much like composing poetry or music." >>> -- Donald Knuth >>> >> >> >
_______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
