You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Morten <li...@kikobu.com> on 2004/12/22 14:31:52 UTC
MS XP client oddities
Hi. I have 2 identical Slide configurations "Good" and "Bad". Both are
RC1 bundled w. Tomcat 5.0.28, and both are unmodified.
"Good" runs on localhost (WinXP), and I can connect fine to that using
WebFolders. "Bad" runs on a remote Linux box, and I can initiate the
connection process, get prompted for login/password, but then connection
process fails (the WebFolders return message is in danish, translated:
"The specified filder is apparently not available. Specify another
folder.").
Both instances have the "OPTIONS" in the log file:
"Bad":
http-80-Processor24, 22-Dec-2004 07:19:41, root, OPTIONS, 200 "OK", 122
ms, /
"Good":
http-8080-Processor25, 22-dec-2004 14:21:18, root, OPTIONS, 200 "OK", 10
ms, /
But for "Bad", that's all there is, whereas for "Good", two PROPFIND's
are also present:
http-8080-Processor25, 22-dec-2004 14:21:18, root, PROPFIND, 207
"Multi-Status", 20 ms, /
http-8080-Processor25, 22-dec-2004 14:21:18, root, PROPFIND, 207
"Multi-Status", 20 ms, /
Can any of you come up with a sound explanation for why I can connect to
"Good", but not "Bad"? They're identical setup's, only port number and
VMs are different.
Br,
Morten
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Robust setup (Was: MS XP client oddities)
Posted by Morten <li...@kikobu.com>.
>> 4. Apache rewrites URLs so DAV repositories are root folders, eg.
>> http://dav.foo.myhost.com/ proxies to http://myhost.com:8080/dav/foo/
>
>
> I'm curious: how is URL rewriting supposed to work with WebDAV? For
> instance, PROPFIND response bodies contain URLs that will not get
> rewritten on their way back to the client, right?
Good point.
It's not feasible to rewrite the returned content as that can
potentially be large amounts of data.
Coming up with a good mod_rewrite conditional URL rewrite scheme might
be an idea. That would place some constraints on what directory names
one can allow in the DAV repository though (as one would need to be
certain that directories starting with eg. /dav/.*/ should be rewritten).
Hmm..
Morten
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Robust setup (Was: MS XP client oddities)
Posted by Julian Reschke <ju...@gmx.de>.
Morten wrote:
>
> Hi,
>
>> http://greenbytes.de/tech/webdav/webdav-redirector-list.html
>> http://greenbytes.de/tech/webdav/webfolder-client-list.html
>
>
> Seen in the light of this, what would you recommend as a robust setup?
> Does Slide put in any extra effort to work around MS client deficiencies?
>
> My list of considerations for a robust setup so far:
>
> 1. Apache running HTTPS in front of Slide (ProxyPass via HTTP)
> 2. Apache proxies so a fixed port is not needed in the URL
> 3. Apache uses mod_auth_msfix for BasicAuth fixes
> 4. Apache rewrites URLs so DAV repositories are root folders, eg.
> http://dav.foo.myhost.com/ proxies to http://myhost.com:8080/dav/foo/
I'm curious: how is URL rewriting supposed to work with WebDAV? For
instance, PROPFIND response bodies contain URLs that will not get
rewritten on their way back to the client, right?
Julian
--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Robust setup (Was: MS XP client oddities)
Posted by Morten <li...@kikobu.com>.
Hi,
> http://greenbytes.de/tech/webdav/webdav-redirector-list.html
> http://greenbytes.de/tech/webdav/webfolder-client-list.html
Seen in the light of this, what would you recommend as a robust setup?
Does Slide put in any extra effort to work around MS client deficiencies?
My list of considerations for a robust setup so far:
1. Apache running HTTPS in front of Slide (ProxyPass via HTTP)
2. Apache proxies so a fixed port is not needed in the URL
3. Apache uses mod_auth_msfix for BasicAuth fixes
4. Apache rewrites URLs so DAV repositories are root folders, eg.
http://dav.foo.myhost.com/ proxies to http://myhost.com:8080/dav/foo/
Other recommendations?
Thanks,
Morten
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
AW: MS XP client oddities
Posted by Daniel Florey <da...@web.de>.
I'd recommend netdrive from novell as WebDAV-client. This one works even in
the dos shell and handles locks and properties. And it's free.
Daniel
> -----Ursprüngliche Nachricht-----
> Von: slide-user-return-10251-daniel.florey=web.de@jakarta.apache.org
> [mailto:slide-user-return-10251-daniel.florey=web.de@jakarta.apache.org]
> Im Auftrag von Morten
> Gesendet: Mittwoch, 22. Dezember 2004 15:12
> An: slide-user@jakarta.apache.org
> Betreff: Re: MS XP client oddities
>
>
> Hi,
>
> Interesting, but depressing, links. Anyway, I changed to WebDrive as DAV
> client in order to troubleshoot a bit further. Apparently it's our
> firewall that blocks the PROPFIND method :-/ (log below).
>
> But what DAV client do you guys usually recommend? Cheap is good...
>
> Thanks,
>
> Morten
>
>
> 12/22/04 15:00:18 D34 [U:] PROPFIND /slide/ HTTP/1.1
> 12/22/04 15:00:18 D34 [U:] Content-Type: text/xml
> 12/22/04 15:00:18 D34 [U:] Depth: 0
> 12/22/04 15:00:18 D34 [U:] Host: www.kikobu.com
> 12/22/04 15:00:18 D34 [U:] User-Agent: WebDrive/6.05 NT DAV
> 12/22/04 15:00:18 D34 [U:] Translate: f
> 12/22/04 15:00:18 D34 [U:] Connection: close
> 12/22/04 15:00:18 D34 [U:] Cookie:
> JSESSIONID=9BDC246ACDF3072464E36F3917EF9053
> 12/22/04 15:00:18 D34 [U:] Authorization: Basic cm9vdDpyb290
> 12/22/04 15:00:18 D34 [U:] <?xml version="1.0" encoding="utf-8"
> ?><propfind
> xmlns="DAV:"><prop><displayname/><lockdiscovery/></prop></propfind>
> 12/22/04 15:00:18 D34 [U:] HTTP/1.0 400 Bad Request
> 12/22/04 15:00:18 D34 [U:] Pragma: no-cache
> 12/22/04 15:00:18 D34 [U:] Cache-Control: no-cache
> 12/22/04 15:00:18 D34 [U:] Content-Type: text/html
> 12/22/04 15:00:18 D34 [U:] Content-Length: 120
> 12/22/04 15:00:18 D34 [U:] 400 Bad Request
> 12/22/04 15:00:18 D34 [U:] <TITLE>Error</TITLE>
> 12/22/04 15:00:18 D34 [U:] <BODY>
> 12/22/04 15:00:18 D34 [U:] <H1>Error</H1>
> 12/22/04 15:00:18 D34 [U:] FW-1 at roskilde: Sorry, the method you tried
> to use is not allowed.</BODY>
> 12/22/04 15:00:18 D34 [U:] Can't connect to WebDAV server at
> http://www.kikobu.com/slide/, 400 Bad Request
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: MS XP client oddities
Posted by Morten <li...@kikobu.com>.
Hi,
Interesting, but depressing, links. Anyway, I changed to WebDrive as DAV
client in order to troubleshoot a bit further. Apparently it's our
firewall that blocks the PROPFIND method :-/ (log below).
But what DAV client do you guys usually recommend? Cheap is good...
Thanks,
Morten
12/22/04 15:00:18 D34 [U:] PROPFIND /slide/ HTTP/1.1
12/22/04 15:00:18 D34 [U:] Content-Type: text/xml
12/22/04 15:00:18 D34 [U:] Depth: 0
12/22/04 15:00:18 D34 [U:] Host: www.kikobu.com
12/22/04 15:00:18 D34 [U:] User-Agent: WebDrive/6.05 NT DAV
12/22/04 15:00:18 D34 [U:] Translate: f
12/22/04 15:00:18 D34 [U:] Connection: close
12/22/04 15:00:18 D34 [U:] Cookie:
JSESSIONID=9BDC246ACDF3072464E36F3917EF9053
12/22/04 15:00:18 D34 [U:] Authorization: Basic cm9vdDpyb290
12/22/04 15:00:18 D34 [U:] <?xml version="1.0" encoding="utf-8"
?><propfind
xmlns="DAV:"><prop><displayname/><lockdiscovery/></prop></propfind>
12/22/04 15:00:18 D34 [U:] HTTP/1.0 400 Bad Request
12/22/04 15:00:18 D34 [U:] Pragma: no-cache
12/22/04 15:00:18 D34 [U:] Cache-Control: no-cache
12/22/04 15:00:18 D34 [U:] Content-Type: text/html
12/22/04 15:00:18 D34 [U:] Content-Length: 120
12/22/04 15:00:18 D34 [U:] 400 Bad Request
12/22/04 15:00:18 D34 [U:] <TITLE>Error</TITLE>
12/22/04 15:00:18 D34 [U:] <BODY>
12/22/04 15:00:18 D34 [U:] <H1>Error</H1>
12/22/04 15:00:18 D34 [U:] FW-1 at roskilde: Sorry, the method you tried
to use is not allowed.</BODY>
12/22/04 15:00:18 D34 [U:] Can't connect to WebDAV server at
http://www.kikobu.com/slide/, 400 Bad Request
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: MS XP client oddities
Posted by Alessandro Apostoli <al...@otssistemi.it>.
Hi Morten...
take a look at this two articles,
http://greenbytes.de/tech/webdav/webdav-redirector-list.html
http://greenbytes.de/tech/webdav/webfolder-client-list.html
it appears that on ports different than 80 you can expect
pretty much anything, like non-ascii URL s not working,
connection failures and the likes.
In my personal experience a Windows XP SP2 + latest fixes with
slide on port 80 as root namespace (that is slide mounted on
http://your.ip.address) is working
Alessandro.
Morten wrote:
>
> Hi. I have 2 identical Slide configurations "Good" and "Bad". Both are
> RC1 bundled w. Tomcat 5.0.28, and both are unmodified.
>
> "Good" runs on localhost (WinXP), and I can connect fine to that using
> WebFolders. "Bad" runs on a remote Linux box, and I can initiate the
> connection process, get prompted for login/password, but then
> connection process fails (the WebFolders return message is in danish,
> translated: "The specified filder is apparently not available. Specify
> another folder.").
>
> Both instances have the "OPTIONS" in the log file:
>
> "Bad":
> http-80-Processor24, 22-Dec-2004 07:19:41, root, OPTIONS, 200 "OK",
> 122 ms, /
>
> "Good":
> http-8080-Processor25, 22-dec-2004 14:21:18, root, OPTIONS, 200 "OK",
> 10 ms, /
>
> But for "Bad", that's all there is, whereas for "Good", two PROPFIND's
> are also present:
>
> http-8080-Processor25, 22-dec-2004 14:21:18, root, PROPFIND, 207
> "Multi-Status", 20 ms, /
> http-8080-Processor25, 22-dec-2004 14:21:18, root, PROPFIND, 207
> "Multi-Status", 20 ms, /
>
> Can any of you come up with a sound explanation for why I can connect
> to "Good", but not "Bad"? They're identical setup's, only port number
> and VMs are different.
>
> Br,
>
> Morten
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: MS XP client oddities
Posted by kranga <kr...@k2d2.org>.
Another culprit (for unicode) is most likely an old version of msdaipp.dll.
If you have version 8.x it fails on unicode. If you have Office 2003 then a
newer version is installed (11.x). That fixes the problem.
1. Open the command prompt and go to c:\program files\common
files\system\ole db
2. Type: regsvr32 /u msdaipp.dll
3. Rename the msdaipp.dll to msdaipp.dll.old
4. Copy the new version to the same directory.
5. Type: regsvr32 msdaipp.dll
----- Original Message -----
From: "Morten" <li...@kikobu.com>
To: <sl...@jakarta.apache.org>
Sent: Wednesday, December 22, 2004 8:31 AM
Subject: MS XP client oddities
>
> Hi. I have 2 identical Slide configurations "Good" and "Bad". Both are
> RC1 bundled w. Tomcat 5.0.28, and both are unmodified.
>
> "Good" runs on localhost (WinXP), and I can connect fine to that using
> WebFolders. "Bad" runs on a remote Linux box, and I can initiate the
> connection process, get prompted for login/password, but then connection
> process fails (the WebFolders return message is in danish, translated:
> "The specified filder is apparently not available. Specify another
> folder.").
>
> Both instances have the "OPTIONS" in the log file:
>
> "Bad":
> http-80-Processor24, 22-Dec-2004 07:19:41, root, OPTIONS, 200 "OK", 122
> ms, /
>
> "Good":
> http-8080-Processor25, 22-dec-2004 14:21:18, root, OPTIONS, 200 "OK", 10
> ms, /
>
> But for "Bad", that's all there is, whereas for "Good", two PROPFIND's
> are also present:
>
> http-8080-Processor25, 22-dec-2004 14:21:18, root, PROPFIND, 207
> "Multi-Status", 20 ms, /
> http-8080-Processor25, 22-dec-2004 14:21:18, root, PROPFIND, 207
> "Multi-Status", 20 ms, /
>
> Can any of you come up with a sound explanation for why I can connect to
> "Good", but not "Bad"? They're identical setup's, only port number and
> VMs are different.
>
> Br,
>
> Morten
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org