Home > webdav propfind > propfind 404 error

Propfind 404 Error

Contents

Next This bug is not in your last search propfind http results. Bug50550 - PropFind 404 error after MkCol succes Summary: PropFind

Webdav Propfind

404 error after MkCol succes Status: RESOLVED FIXED Product: Tomcat 5 Classification: Unclassified Component: Servlets:WebDAV Version:

Propfind Method Vulnerability

5.5.31 Hardware: PC Windows XP Importance: P2 normal (vote) TargetMilestone: --- Assigned To: Tomcat Developers Mailing List URL: Keywords: Depends on: Blocks: Show dependency tree

Webdav Propfind Example

Reported: 2011-01-06 09:11 UTC by Maarten van Hulsentop Modified: 2011-01-20 14:23 UTC (History) CC List: 0 users Attachments Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description Maarten van Hulsentop 2011-01-06 09:11:12 UTC A propfind propfind attack call on a resource returns a 404 error when executed after a mkcol for the same resource. The mkcol should be preceeded with a propfind to trigger the issue. Steps to reproduce - See the following access log; 127.0.0.1 - - [06/Jan/2011:14:09:19 +0100] "PROPFIND /webdav/output/f469e3d6-e536-4072-82da-d989acaf57a2/ HTTP/1.1" 404 1084 127.0.0.1 - - [06/Jan/2011:14:09:19 +0100] "MKCOL /webdav/output/f469e3d6-e536-4072-82da-d989acaf57a2/ HTTP/1.1" 201 - 127.0.0.1 - - [06/Jan/2011:14:09:19 +0100] "PROPFIND /webdav/output/f469e3d6-e536-4072-82da-d989acaf57a2/ HTTP/1.1" 404 1084 When the first request would be omitted, the third request would have been succesful, as the following access log shows; 127.0.0.1 - - [06/Jan/2011:14:10:39 +0100] "MKCOL /webdav/output/81a97360-ea49-44d3-b764-d8c7e60e885e/ HTTP/1.1" 201 - 127.0.0.1 - - [06/Jan/2011:14:10:39 +0100] "PROPFIND /webdav/output/81a97360-ea49-44d3-b764-d8c7e60e885e/ HTTP/1.1" 207 628 Note: After a few seconds, the response to propfind for that resource is OK again. This suggests this has to do with caching. Note2: This situation sounds similar to call 21288 (FIXED - 'DirContext caching problem with Dreamweaver 6 when recursively creating directories'). Reproducable using a jackrabbit clie

Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums Home IIS.NET Forums IIS 7 and Above ASP.NET Administration Error 404 Method Not Allowed - curl propfind ASHX handler - PROPFIND Error 404 Method Not Allowed - ASHX handler propfind apache - PROPFIND [Answered]RSS 1 reply Last post Dec 02, 2011 03:32 AM by Lloydz ‹ Previous Thread|Next Thread › propfind in logs Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Advanced Search Reply evildregs 1 Post Error 404 Method Not Allowed - ASHX handler - PROPFIND Nov 29, 2011 03:30 https://bz.apache.org/bugzilla/show_bug.cgi?id=50550 AM|evildregs|LINK Before I even start I want to say that the other troubleshooting about Method Not Allowed didn't work, so please read what I've done and respond appropriately. First, I'm implementing a custom WebDAVapp with ASP.NET 4.0 64-bit app hosted in IIS 7.0. It's accessing a custom data store so I don't think I can just use existing WebDAV modules. Whenever I try to https://forums.iis.net/t/prev/1183145 initially connect a PROPFIND request is issued, which first gets rejected with unauthorized, then I enter credentials, then it gets rejected with error 404 - Method Not Allowed. I removed every single handler in the Handler Mappings so I know for sure which one I'm using - the SimpleHandlerFactory-Integrated handler. I've changed the request restrictions so that All Verbs are allowed - which made no difference. I then changed to "One of the following verbs:" and added every verb I need (and all matching the case i see in my network traces). No matter what I do, the PROPFIND request fails, and returns a response with Allow: GET, HEAD, OPTIONS, TRACE, LOCK, UNLOCK. Where in the world is that coming from? I can't find that list of verbs anywhere. Is this hard-coded in ASP.NET? I can supply the fully request and response traces if needed. Please help, I'm lost. error asp.net verb allow 4.0 404 http ashx PROPFIND Reply Lloydz 2318 Posts Re: Error 404 Method Not Allowed - ASHX handler - PROPFIND Dec 02, 2011 03:32 AM|Lloydz|LINK Hi, I suggest you double check the following: 1. Request fi

feature requests Search HTTP 404 error by accesing to ownCloud using https://forum.owncloud.org/viewtopic.php?t=7752 mobile apps You found a bug or you're missing a major feature? Just ask and discuss Forum rules The forums were migrated over to https://central.owncloud.org which is based on the forum software Discourse. The forums here is put into read-only mode starting from today.More background information about webdav propfind this move and the reasoning behind it is available in this blogpost:https://daniel.molkentin.net/2016/07/20 ... d-central/ Locked Print view Search Advanced search 3 posts • Page 1 of 1 rperez Newbie Posts: 2 Joined: Mon Jan 21, 2013 11:12 am ownCloud version: 4.5.5 HTTP 404 error by accesing to propfind 404 error ownCloud using mobile apps Quote Postby rperez » Mon Jan 21, 2013 11:19 am By accessing to ownCloud using the mobile apps, a user is having a 404 error.Any idea on how to configurate properly the server?The server logs are:........HTTP/1.1 200 OKCache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0Pragma: no-cacheContent-Type: text/htmlExpires: Thu, 19 Nov 1981 08:52:00 GMTServer: Microsoft-IIS/7.5X-Powered-By: PHP/5.3.19X-Powered-By: ASP.NETDate: Thu, 17 Jan 2013 11:48:01 GMTContent-Length: 76{"installed":"true","version":"4.90.6","versionstring":"4.5.5","edition":""}PROPFIND /owncloud/remote.php/webdav/ HTTP/1.1Host: mfg.dtdns.netDepth: 1Accept-Encoding: gzip, deflateContent-Type: application/xmlAccept-Language: es-esAccept: */*Content-Length: 92Connection: keep-aliveUser-Agent: Owncloud%20iOs%20Client/2.08 CFNetwork/609 Darwin/11.4.2HTTP/1.1 404 Not FoundContent-Type: text/htmlServer: Microsoft-IIS/7.5X-Powered-By: ASP.NETDate: Thu, 17 Jan 2013 11:48:13 GMTContent-Length: 1251404 - Kan bestand of map niet vinden.