Method PROPFIND is not is not implemented

Question

The customer was facing this recurring:

2016-07-04 06:53:33,937: ERROR [ErrorLoggingFilter] - Method PROPFIND is not is not implemented by this servlet for this URI

What is the meaning of this error?

Answer

This error happens because a third party is trying to use HTTP method PROPFIND when calling the Jahia server, and Jahia does not implement such a method, only if a call is done with the WebDAV servlet as defined in the web.xml file :
 

<!-- ====================================================================== -->
<!-- W E B D A V S E R V L E T -->
<!-- ====================================================================== -->
<servlet>
    <description>
        The webdav servlet that connects HTTP request to the repository.
    </description>
    <servlet-name>Webdav</servlet-name>
    <servlet-class>org.apache.jackrabbit.j2ee.JahiaWebdavServlet</servlet-class>
    <init-param>
        <description>
            defines the prefix for spooling resources out of the repository.
        </description>
        <param-name>resource-path-prefix</param-name>
        <param-value>/repository</param-value>
    </init-param>
    <!--
    Optional parameter to define the value of the &#quot;WWW-Authenticate&#quot; header
    -->
    <init-param>
        <description>
            Defines the value of the &#quot;WWW-Authenticate&#quot; header.
        </description>
        <param-name>authenticate-header</param-name>
        <param-value>Basic realm="Digital Factory WebDAV Server"</param-value>
    </init-param>
    <!--
    -->
    <!--
    Parameter used to configure behaviour of webdav resources such as:
    - destinction between collections and non-collections
    - resource filtering
    -->
    <init-param>
        <description>
            Defines various dav-resource configuration parameters.
        </description>
        <param-name>resource-config</param-name>
        <param-value>/WEB-INF/etc/repository/jackrabbit/webdav-config.xml</param-value>
    </init-param>
    <load-on-startup>4</load-on-startup>
</servlet>

However,  this error can be safely ignored and/or blocked by your Web server (consult your system administrator to block such requests).