Re: Getting xml-rpc and w.bloggar to work

On Thu, 2003-08-07 at 16:33, Wari Wahab wrote:
> Most of the fixes would actually
> involve massaging all the Windows representations of \ to / and back (to
> w.bloggar, convert \ to /, and from wbloggar, convert / to \)
> 
> I'll also have to see why authentication doesn't work on Windows, weird.

I did some preliminary investigation with a pyblosxom installation on a
Win2K, apache as the server, activestate python 2.2.2, and about a few
hundred text entries. The pyblosxom part went well, and looks ok to me
(I didn't look really far though).

I tested the xmlrpc part, doing a `s.blogger.getUsersBlogs('',
'someuser', 'somepassword')` in python works fine, that is, after
declaring py['base_url'] and also added a line in the
blogger_getUsersBlogs() function in blogger.py:
blogpath = blogpath.replace(os.sep, '/')

That looks good, testing it with w.bloggar however is a nightmare. 

I added a line to see what's wrong in getUsersBlogs:
file('debug.txt','w').write('getUsersBlogs: user "%s" pass "%s"') <- erm
why is the windows apache webserver weak in security on a default
install? 

Looked at the debug file and immediately find what why the username is
wrong. Somehow, both username and password are blank. This looks a lot
deeper than anything else I've encountered. I'm not sure where the bug
is, xmlrpclib? w.bloggar? apache? Win2K?

This happens when I used the 'Reload Blog List' button. If I clicked ok
(where you got the not well-formed XML parser error) the debug file gets
filled with the username and password.

These things don't happen when I'm on a unix host though. I need to
probe deeper when I'm free, but right now, I've got a bad feeling about
this.


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01