Hi,
I am using jakarta-slide with davfs2, which in turn uses the neon
library. I do not know why, but when I tried to mount a webdav fs, the
slide webapp responded with the 302 http status code (moved
temporarily). This causes the davfs to fail the mounting operation.
I traced the error back to neon library, and then I found these kind
of checks inside the ne_basic.c module:
if (ret == NE_OK && ne_get_status(req)->klass != 2)
{
*modtime = -1;
ret = NE_ERROR;
}
Where klass seems to be the first digit of the http status code. I
changed the lines mentioned above in order to consider as a success
the 302 case, it was something like:
if (ret == NE_OK && ne_get_status(req)->klass != 2 &&
ne_get_status(req)->code != 302)
{
*modtime = -1;
ret = NE_ERROR;
}
(yes, I know that modifying all these line in that way is not modular,
but I only wanted a dirty-quick work around for testing purposes ;-)
The point is that after these changes, davfs seemed to work pretty
well ( I could mount and operate the webdav fs normally ). So, my
question: Is slide (or maybe tomcat) wrong in returning these 302
codes, or neon should treat them in a different way?
Thanks in advance.
dario estepario.
PS: I am using these versions:
1. neon-0.24.7
2. jakarta-tomcat-5.5.9
3. jakarta-slide-2.2
_______________________________________________
neon mailing list
[email protected]
http://mailman.webdav.org/mailman/listinfo/neon
