Re: somewhat off topic: managing Win32 limits in WebDAV

I need to join the other list.

I am dealing with a server side limitation. Our set up is Apache 2.2 on
Windows XP Pro for the moment. We wrote our own client and the URL limit is
10,000,000. Probably excessive but there you go.

In our tests, Apache reports a 403 error but that appears to be misleading.
Further testing reveals a "magic" limit where URI's between 249 and 260
characters in length fail on the MKCOL command.

So our supposition is the ever-popular MAX_PATH constraint. Of course, that
may not be the issue and we open to new info.

thanks for the reply,

 - Mark




On 12/10/08 9:33 AM, "Julian Reschke" <julian.reschke@gmx.de> wrote:

> 
> Mark Phillips wrote:
>>   I would be most grateful for information and/or links to articles that
>> describe how others have dealt with the 260 character path limit in
>> Windows. The product manager I work with feels we must support Windows
>> as a backend for the DAV enable product we are developing. Testing with
>> a few clients has exposed the Win32 limitation in a rather stark way.
>> 
>> Thank you, in advance.
>> 
>> Mark Phillips
> 
> Hi Mark,
> 
> it seems to be you selected a non-optimal list for this question :-) --
> w3c-dist-auth@w3.org (the generic WebDAV mailing list) seems to be a
> better choice.
> 
> That being said -- are you referring to a limit on the client or on the
> server?
> 
> In general, Windows can deal with longer paths, you just need to use the
> correct API for that. If course, many Windows *applications*, such as
> Explorer, don't.
> 
> BR, Julian
> 
>

Received on Wednesday, 10 December 2008 21:05:38 UTC