Unanswered

Active Topics

Forums

Forums > Document Exchange 4 and 5 > WebDAV

Subject: 404 when using WebDav

Prev Next

You are not authorized to post a reply.

Author

Messages

Robb Bryn
Posts:16

02/09/2010 16:51:50

Alert

when I try to "open in windows explorer" nothing happens. digging a bit deeper with fiddler shows some 404 errors. This is on a fresh install of DMX 5.2.2 There were no errors on the install and right now there is one folder (called template) off the root that I am trying to access.

This is on IIS 6, Network service has full privilages to all folders in DNN and the verb options have been adjusted per the install doc for the .axd extension. wildcard mapping has also been confirmed as instructed via the docs. One discrepency I found was in the web.config. The documentation mentions the following line;

path="/" verb="OPTIONS,PROPFIND" type="Bring2mind.DNN.Modules.DMX.WebDAV.DavHandler, Bring2mind.DNN.Modules.DMX.WebDAV" validate="false" />

it added this instead

path="*" verb="OPTIONS,PROPFIND" type="Bring2mind.DNN.Modules.DMX.WebDAV.DavHandler, Bring2mind.DNN.Modules.DMX.WebDAV" validate="false" />

Everything else appears to be in order.

Trace from fiddler;

# Result Protocol Host URL Body Caching Content-Type Process Comments Custom

6 404 HTTP admin.monteithco.com / 1,635 text/html iexplore:3036

7 404 HTTP admin.monteithco.com /dmxdav.axd/Template 1,635 text/html iexplore:3036

8 404 HTTP admin.monteithco.com /_vti_inf.html 1,635 text/html iexplore:3036

9 404 HTTP admin.monteithco.com /_vti_bin/shtml.exe/_vti_rpc 1,635 text/html iexplore:3036

10 404 HTTP admin.monteithco.com / 1,635 text/html iexplore:3036

11 404 HTTP admin.monteithco.com /dmxdav.axd/Template 1,635 text/html iexplore:3036

Peter Donker

Posts:2973

02/09/2010 22:34:25	Alert
Hi Robb, The wildcard is fine. But to dig deeper we need to look at the response headers of the 404s. Can you show those? They will indicate whether the call was being routed to DMX and whether it picked it up. Use for instance Raw view to see them. Peter

Robb Bryn
Posts:16

02/09/2010 22:43:58

Alert

The Response header (raw) isn't healping much either... here's what it's showing for the call to /dmxdav.axd/Template

it's just a plain ole 404 error page.

OPTIONS http://mysite.com/ HTTP/1.1
Translate: f
User-Agent: Microsoft Data Access Internet Publishing Provider Protocol Discovery
Host: mysite.com
Content-Length: 0
Connection: Keep-Alive
Pragma: no-cache
Cookie: .ASPXANONYMOUS=LlK6C4v... etc

HTTP/1.1 404 Not Found
Content-Length: 1635
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 09 Feb 2010 21:38:58 GMT

The page cannot be found

The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Please try the following:

Make sure that the Web site address displayed in the address bar of your browser is spelled and formatted correctly.
If you reached this page by clicking a link, contact
the Web site administrator to alert them that the link is incorrectly formatted.
Click the Back button to try another link.

HTTP Error 404 - File or directory not found.
Internet Information Services (IIS)

Technical Information (for support personnel)

Go to Microsoft Product Support Services and perform a title search for the words [b]HTTP[/b] and [b𖳜[/b].
Open [b]IIS Help[/b], which is accessible in IIS Manager (inetmgr),
and search for topics titled [b]Web Site Setup[/b], [b]Common Administrative Tasks[/b], and [b]About Custom Error Messages[/b].

Robb Bryn
Posts:16

02/11/2010 16:20:52	Alert
Found the problem... URLScan was running on the Server and only allowing GET/HEAD/POST. turned it off the verb checking and all works now.

Robb Bryn
Posts:16

02/11/2010 16:47:24	Alert
OK, here's the full info in case anyone runs into this in the future. URLScan will throw a 404 error on any WebDav requests and block access entirely to a file with the .axd extension. Out of the box, URL scan only allows the common extentions and the normal GET/HEAD/POST verbs, the others are denied. In addition, there is a [DENY HEADERS] section in the urlscan.ini that specifically denies any header related to WebDAV (translate: if: lock-token: transfer-encoding:). To get DMX running with Webdav you must allow all the verbs, and remove the deny headers section. Once removed you should be able to run DMX with no problems.

Peter Donker

Posts:2973

02/12/2010 20:30:50	Alert
Thanks for the info Robb ... much appreciated.

You are not authorized to post a reply.

Forums > Document Exchange 4 and 5 > WebDAV > 404 when using WebDav

ActiveForums 3.6

The page cannot be found

HTTP Error 404 - File or directory not found. Internet Information Services (IIS)

HTTP Error 404 - File or directory not found.
Internet Information Services (IIS)