Thu 22 Dec 2011 11:23:53 PM UTC, comment #6:
Hi Werner,
first of all, sorry for my late reply.
I can confirm that your two patches as attached to comment #5 (file #24621, file #24622) replacing my proposed patch also work fine to access my main Oracle Beehive WebDAV server.
And yes, you were indeed right that I introduced a severe bug to turn off rfc_quota on any error (including connection timeout)... ;-)
Regarding the cookie issue:
This issue only applies to the other WebDAV resource I am also accessing, it seems to establish two cookies both named JSESSIONID containing just a simple log string (an encrypted Java EE session ID), but for different contexts: one for a context named "/content", the other for a context named "/teamcollab".
For accessing the files via WebDAV, it will then need the "/content" cookie to be sent ("real" resource context path starts looks like content/dav/Oracle/XXX/...).
I am not completely sure whether it is this fact which makes your original cookie code fail, but the code from
http://savannah.nongnu.org/support/?107764
definitely seemed to work for me while the original did not.
If you need more details, I will also be able to send the full cookie information via direct mail to you (I don't want to disclose particular server name and cookie content...).
Many thanks anyway for the two official patches that now make Beehive WebDAV work properly with davfs2 - I will also try and advertise the fact that davfs2 now works fine for accessing their WebDAV with the Beehive team within Oracle...
Also, when I have more time, I may again look into the log details for the other resource without the cookie patch...
Merry Christmas and Happy Holidays!
Best regards,
Andreas
|