Background
RFC2616 spec at http://www.ietf.org/rfc/rfc2616.txt
defines this set of common methods for HTTP/1.1:
OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, CONNECT
WebSphere's plug-in by default supports all above access methods. In
addition, by default the plug-in expects and reads content for POST and
PUT requests only in the case that Content-Length or Transfer-encoding
headers are present in the http request. By default, for other access
methods plug-in does not accept by default any data followed by
Content-Length or Transfer-Encoding http header.
It usually causes problems when access method is one of WebDAV extensions,
such as PROPFIND, because in most cases the http request with WebDAV
extensions includes also data (or we can also say that the http request
contains a body).
Solution:
The fix PQ76729 enhanced WebSphere plug-in so that a client can send data
on all http requests from HTTP 1.1 spec (such as POST, PUT, GET, HEAD)
when Content-Length or Transfer-encoding header is present in the request
headers. In addition, this fix enables also WebDAV extensions to contain
data in the http request.
To enable this feature execute these steps:
- Verify that you upgraded to the latest Cumulative plugin
fix which includes PQ76728
- Set AcceptAllContent property in Config element of the
plugin-cfg.xml to true.
Example: <Config AcceptAllContent="true">
More information about WebDAV extensions can be found on this Web site:
http://www.webdav.org/
Conclusion
This document should be used as a guideline toward the WebDAV extensions
enablement in WebSphere 4.0 or 5.0 plug-in. |