Forum OpenACS Q&A: Problem with webdav - daveb?

Collapse
Posted by Cathy Sarisky on
I had webdav working last week on a 5.2.3 instance. It's not working now, and unfortunately, I'm not sure what's changed. I can't access folders (in "my network places" on windows) that I created last week, nor can I create new folders. I -can- get as far as putting in my password when I try to connect to a particular folder for the first time, but I get this error message:

[18/Aug/2007:17:00:14][26010.7176][-conn:chem_new::4] Error: bad option "uri": must be authpassword, authuser, close, content, contentlength, copy, driver, encoding, files, fileoffset, filelength, fileheaders, flags, form, headers, host, id, isconnected, location, method, outputheaders, peeraddr, peerport, port, protocol, query, request, server, sock, start, status, url, urlc, urlencoding, urlv, version, or write_encoded
bad option "uri": must be authpassword, authuser, close, content, contentlength, copy, driver, encoding, files, fileoffset, filelength, fileheaders, flags, form, headers, host, id, isconnected, location, method, outputheaders, peeraddr, peerport, port, protocol, query, request, server, sock, start, status, url, urlc, urlencoding, urlv, version, or write_encoded
while executing
"ns_conn $var"
("default" arm line 2)
invoked from within
"switch $var {
locale {
set ad_conn(locale) [parameter::get -parameter SiteWideLocale -package_id [apm_pa..."
("default" arm line 7)
invoked from within
"switch $var {
form {
return [ns_getform]
}
all {
return [array get ad_conn]
..."
("-get" arm line 10)
invoked from within
"switch -- $flag {
-connected_p {
return [info exists ad_conn(request)]
}

-set {
set ad_conn($var) [lindex $args 2]
}

..."
(procedure "ad_conn" line 12)
invoked from within
"ad_conn $var"
("-get" arm line 5)
invoked from within
"switch -- $flag {
-set {
set value [lindex $args 2]
set tdav_conn($var) $value
return $value
}
..."
(procedure "oacs_dav::conn" line 10)
invoked from within
"oacs_dav::conn uri"
(procedure "oacs_dav::handle_request" line 3)
invoked from within
"oacs_dav::handle_request cns83 {}"
[18/Aug/2007:17:00:14][26010.6151][-conn:chem_new::3] Error: bad option "uri": must be authpassword, authuser, close, content, contentlength, copy, driver, encoding, files, fileoffset, filelength, fileheaders, flags, form, headers, host, id, isconnected, location, method, outputheaders, peeraddr, peerport, port, protocol, query, request, server, sock, start, status, url, urlc, urlencoding, urlv, version, or write_encoded
bad option "uri": must be authpassword, authuser, close, content, contentlength, copy, driver, encoding, files, fileoffset, filelength, fileheaders, flags, form, headers, host, id, isconnected, location, method, outputheaders, peeraddr, peerport, port, protocol, query, request, server, sock, start, status, url, urlc, urlencoding, urlv, version, or write_encoded
while executing
"ns_conn $var"
("default" arm line 2)
invoked from within
"switch $var {
locale {
set ad_conn(locale) [parameter::get -parameter SiteWideLocale -package_id [apm_pa..."
("default" arm line 7)
invoked from within
"switch $var {
form {
return [ns_getform]
}
all {
return [array get ad_conn]
..."
("-get" arm line 10)
invoked from within
"switch -- $flag {
-connected_p {
return [info exists ad_conn(request)]
}

-set {
set ad_conn($var) [lindex $args 2]
}

..."
(procedure "ad_conn" line 12)
invoked from within
"ad_conn $var"
("-get" arm line 5)
invoked from within
"switch -- $flag {
-set {
set value [lindex $args 2]
set tdav_conn($var) $value
return $value
}
..."
(procedure "oacs_dav::conn" line 10)
invoked from within
"oacs_dav::conn uri"
(procedure "oacs_dav::handle_request" line 3)
invoked from within
"oacs_dav::handle_request cns84 {}"
[18/Aug/2007:17:00:15][26010.5126][-conn:chem_new::2] Error: return: failed to redirect '404': exceeded recursion limit of 3

This is webdav version 1.1b1 according to the .info file.

Thanks in advance for any hints!

Collapse
Posted by Michael Aram on
Hi!

I´m facing the same problem! What was your solution?

Collapse
Posted by Dave Bauer on
To track this down would require additional information.

Check to make sure the filters are registered for the URL you are trying to access. There should be information in the error log when they are registered.