At 02:44 PM 11/20/01 -0600, Ian Bicking wrote:
>On Tue, 2001-11-20 at 14:16, Geoff Talvola wrote:
> > First, make sure that the Application.config setting
> > IncludeTracebackInXMLRPCFault is set to 1. I think it is set to 1 by
> > default, but I'm not positive. What this means is that if your X
On Tue, 2001-11-20 at 14:16, Geoff Talvola wrote:
> First, make sure that the Application.config setting
> IncludeTracebackInXMLRPCFault is set to 1. I think it is set to 1 by
> default, but I'm not positive. What this means is that if your XML-RPC
> method raises an exception, the text of th
At 01:22 PM 11/20/01 -0600, Ian Bicking wrote:
>On Tue, 2001-11-20 at 07:10, Geoffrey Talvola wrote:
> > You could make it easier by writing a wrapper around the XML-RPC client
> > libraries to automatically add in the username and password to every
> request,
> > and similar handling on the serv
On Tue, 2001-11-20 at 07:10, Geoffrey Talvola wrote:
> You could make it easier by writing a wrapper around the XML-RPC client
> libraries to automatically add in the username and password to every request,
> and similar handling on the server side to validate them (i.e. a
> SecureXMLRPCServlet
On Monday November 19, 2001 09:36 pm, Ian Bicking wrote:
> I'm just curious: how are people doing authentication with XML-RPC? Do
> you just have every request include a username/password to authenticate
> that particular request/action?
>
> Ian
That's the way we do it. We also use https to p
I'm just curious: how are people doing authentication with XML-RPC? Do
you just have every request include a username/password to authenticate
that particular request/action?
Ian
___
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.
