> >
> > Yes, it's quite possible that it's a time-out. Neon (the client-side
> > http library) is probably timing out after 90 secs...
> >
>
> Ok, I try to compile neon with a bigger timeout and see what will
happen...
>
I have set the SOCKET_READ_TIMEOUT from 120 to 12000, but this doesn't
change anything, since it had stop before 120secs are over, this isn't very
suprising...
> >
> > Regardless, repeat the expermiment while using Ethereal to capture the
> > data. When the client dies, take a look at the HTTP dialogue and see
> > how much data was sent.
> >
>
The client sends the PROPFIND for the directory and server doesn't send any
answer to back to the client. Just closeing the connection after a while. I
have rerun this serveral times, the time it takes changes, so it doesn't
seems like a timeout. Would have been too easy :-(
Also ethereal shows that nothing is send back to the client, the access_log,
says status 207 and 900 Bytes for that PORPFIND request. There is nothing in
the error_log. Strange....
If this doesn't makes sense to anybody, seems like I have to try the
debugger when I get some time....
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: richter@ecos.de Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 4 22:01:38 2002