OBD crafts the Authorization header for the request and hands that String to the URL Fetch Service to send. I should thank you really since I simply integrated your workaround.
Matt On Wed, Jan 6, 2010 at 11:29 AM, Jeff Lucido <[email protected]> wrote: > Great. I downloaded the new engine, installed and added back the username > and password attributes and it works as expected. > > Just curious and for my own understanding; under the hood does OBD take > these attribute values and craft the Authorization header for the HTTP > request or does it pass them in another fashion? > > Thanks for the help. I am glad it was something simple. > > Kind regards, > -JSLucido > > On Tue, Jan 5, 2010 at 10:30 AM, Alan Williamson <[email protected]> wrote: >> >> I've just updated the "nightly" build to include this fix from Matt. >> >> So you can grab the Google GAE OpenBD from the usual place >> >> >> Matthew McGinty wrote: >>> >>> I've just checked-in the change that fixes this issue. >>> Basically (pun intended) cfHttpConnectionGoogle.authenticate() needed >>> to be implemented. >> >> -- >> aw2.0 >> http://www.aw20.co.uk/ >> >> >> -- >> Open BlueDragon Public Mailing List >> http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon >> mailing list - http://groups.google.com/group/openbd?hl=en >> >> !! save a network - please trim replies before posting !! > > > -- > Open BlueDragon Public Mailing List > http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon > mailing list - http://groups.google.com/group/openbd?hl=en > > !! save a network - please trim replies before posting !! >
-- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
