Serving HTTP OPTIONS requests to the server context root by WebDAV clients
Some WebDAV clients send an HTTP OPTIONS request to the server context root ( / ) to check whether the server supports WebDAV. To support these clients, the portal provides a web application called wp.webdav.options.war we can enable. This application responds to such requests with a confirmation the portal supports WebDAV.
To enable this WAR file, adapt the application.xml files of the deployed Enterprise Application (EAR), wps.ear, so that wp.webdav.options.war is mapped to the context root ( / )...
- Export the EAR, wps.ear, through the WAS console.
- Open a command prompt.
- Expand the EAR:
- ./EARExpander.sh|bat -ear directory/WebDAV_for_WebSphere_Portal.ear -operationDir directory webdav_expanded -operation expand
- Locate the file application.xml in the expanded EAR file directory.
- Edit the file application.xml of the exported EAR, and uncomment or add the following section:
<module> <web> <web-uri>wp.webdav.options.war</web-uri> <context-root>/</context-root> </web> </module>
- Collapse the EAR:
EARExpander.sh|bat -ear directory/wps.ear -operationDir directory/wps_expanded -operation collapse
- Update the enterprise application with these changes using the WAS console.
- Save the changes.
- Restart the portal for the changes to take effect.
What to do next
Depending on how the web server is set up, this change might cause all requests to be routed to the web server plug-in. In this case refer to the web server documentation for information about how to route only OPTIONS requests to the plug-in.