Re: C#/Mono/CookComputing & xmlrpc2

Helge Hess <[email protected]>
Newsgroups gmane.comp.cms.opengroupware.xmlrpc.devel
Message-ID <[email protected]>
On Jan 29, 2004, at 2:02 PM, Adam Williams wrote:
> "Mogi" :)  I'm shamelessly stealing ideas from JOGI about how to go
> about it.

;-)

>> Do the "other XML-RPC servers" also use basic authentication?
> I think so,  I'll double check exactly how they process authentication;
> but I think that guy left for a mediterranean cruise yesterday.  Darn;
> at least for me.

Hm. I guess they don't ;-) On the other side, if those other servers 
may have a full HTTP/1.1 implementation and work just fine with the 
100-continue issue.

>>> Output in RPC server log - note 401 "authentication failed" code -
>>> -----------------------------------------------------------------
>>> 192.168.1.20 - - [28/Jan/2004:03:43:34 GMT] "POST /RPC2 HTTP/1.1" 
>>> 401 0
>>> 0.003 - - 0
>> This is just fine. After that Mono needs to retry the request using 
>> the
>> proper credentials as requested by the daemon.
> Ok, just never see another try.  This is "preauthenticate" in HTTP
> parlance, yes?

No. Preauthenticate means that the credentials are embedded in the very 
first request (so that the 401 is unnecessary in case the credentials 
are OK). This way you can save one HTTP cycle.

>>> Pukes, after a long pause, with -
>>                   ^^^
>> This looks like the issue I run into. Which Mono version do you use?
>> .28 or .29?
>
> 0.29.  From the red-carpet channel.  Eagerly awaiting 0.30 which has
> lots of other fixes in it; although I have no idea if it will affect
> this issue.

I would like to check, but I'm really busy right now ... :-|

I think the 100-continue issue is even recorded in Bugzilla.

regards,
   Helge
-- 
OpenGroupware.org => http://www.opengroupware.org/

-- 
OpenGroupware.org XML-RPC
[email protected]
http://mail.opengroupware.org/mailman/listinfo/xmlrpc
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.