|
Problem(Abstract) |
This technote provides information on methods that can be
forwarded by Caching Proxy.
The minimum release levels that support this enhancement are: 5.0.2.39,
5.1.1.18, 6.0.2.2.
In addition to support of standard HTTP methods, Caching Proxy supports
forwarding other methods defined in RFCs or used by some applications.
Caching Proxy also supports customer defined methods and allows them to be
forwarded through the proxy server. |
|
|
|
Resolving the
problem |
Web-based Distributed Authoring and Versioning (WebDAV) is
a set of extensions to the HTTP protocol that allows you to
collaboratively edit and manage files on remote Web servers.
Caching Proxy now supports eight HTTP methods, eight WebDAV methods, and
twelve methods used by Microsoft® Exchange Server and other servers. These
methods are hard-coded and are enabled by the Enable/Disable directives.
Administrators can also use the corresponding method-mask defined in the
PROTECT directive to authorize the use of these methods.
Supported methods:
HTTP methods (defined in RFC 2616):
HEAD, GET, POST, PUT, DELETE, OPTIONS, TRACE, CONNECT (used in forward
proxy configuration)
WebDAV methods (defined in RFC 2518):
PROPFIND , PROPPATCH , MKCOL, COPY, MOVE, LOCK, UNLOCK, SEARCH
Microsoft Exchange Server methods:
BMOVE, BCOPY, BDELETE, BPROPFIND, BPROPPATCH, POLL, NOTIFY, SUBSCRIBE,
UNSUBSCRIBE, ACL, SUBSCRIPTIONS, X_MS_ENUMATTS
Note: When the WebDAV or Microsoft Exchange Server methods are
enabled, Caching Proxy forwards the requests to the target servers only
and does not rewrite any resource link in the request body.
Caching Proxy can also forward user-defined methods to the back-end
server. Use the following syntax for the Enable directive in the
ibmproxy.conf file to enable a customized method:
Enable user-defined-method[WithBody |
WithoutBody]
Setting a value of WithBody or WithoutBody indicates to
the proxy if the user-defined method needs a request body.
The following example enables a user-defined method My_METHOD and
indicates to the proxy that the method needs a request body:
Enable MY_METHOD WithBody |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|