Hello Justin,

Thursday, January 11, 2007, 12:56:55 AM, you wrote:

JE> On 1/10/07, Robert Milkowski <[EMAIL PROTECTED]> wrote:
>> According to documentation it should.
>> But I didn't manage to compile it on snv_54.
>> I installed openldap from Blastwave and compiled against it - worked
>> perfectly.

JE> I don't have a snv_54 build locally, but if you can provide the
JE> compilation errors, I might be able to help.  (I'd recommend using
JE> httpd 2.2.4 which was just released.)

I'll sent errors tomorrow.
With 2.2.4 I had some problems with mod_encoding.


>> btw: has anyone tried Sun's webserer as WebDAV server for Windows
>> clients? I'm playin with Apache 2.x + web_dav + web_davfs +
>> mod_encoding + mod_auth_ldap + ... and it's a nightmare.

JE> Subversion serves just fine to Windows boxes from Solaris.  Adding
JE> LDAP authentication is fairly trivial (once it compiles).  What's the
JE> problem?  -- justin

subersion? I lost you.

And the problem - basic authentication works, with digest I always
get internal error - but it could be still due to misconfiguration on
my side - I'll try more tomorrow.


The problem is then when using WebDAV from Windows XP over https or
http with authorization then for example double-clicking on picture
won't open preview - however I can copy file to local storage from web
dav and then it works. With http without password it works fine. The
only difference I see on Windows box is that with webdav over http without
password I see '\\server' in url, while when adding webdav resource
over https or http with password I don't get \\server but rather
http[s]://server and then functionality is limited.

The same is if I want to map webdav resource to disk drive letter -
works only with webda over http without password.

I know it can be configured... :)))

-- 
Best regards,
 Robert                            mailto:[EMAIL PROTECTED]
                                       http://milek.blogspot.com

_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to