BEA Apache connector bug

Question

I'd like to open a bug regarding the Apache connector. We first ran into it back in 7.0 and I just confirmed today it still exists in 8.1 (at least Apache 2.0/win32).
The bug is that the connector only forwards bodies for a subset of HTTP methods, so Webdav, for instance, is unusable via the connector.
For instance, the ACL method, RFC 3744, when sent to apache looks similar to
--- snip --
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: close
<?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:">
<D:ace>
<D:principal>
<D:href>xxx</D:href>
</D:principal>
<D:grant>
<D:privilege> <D:read/> </D:privilege>
</D:grant>
</D:ace>
</D:acl>
but the BEA connector forwards this to BEA as:
-- snip---
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: Keep-Alive
WL-Proxy-SSL: false
WL-PATH-TRIM: /
WL-Proxy-Client-IP: 127.0.0.1
Proxy-Client-IP: 127.0.0.1
X-Forwarded-For: 127.0.0.1
X-WebLogic-Force-JVMID: unset
... which of course times out since the body is not sent but CL is (correctly) specified.
We have to ship our product with a separate apache module which changes all methods to a POST, then stuffs the real method in a header. Then in our special servlet that we ship just for BEA, we extract the real method from the header and use it instead of the POST in the ServletRequest.
Can someone with karma at BEA file this bug? Other methods with bodies that I suspect will probably fail include OPTIONS, PROPPATCH, & PROPFIND. I also verified that arbitrary (ie non-RFC'd) http methods will fail to transmit a body as well.
Our last customer who used our application with BEA was supposed to open a bug about this via standard support means but I don't have any record of it ever being done.
Thanks,
Keith

Answer 1

Hi. Please send me an email address and I'll do what I can.
j
o
e
b
e
a
c
o
m
Keith Wannamaker wrote:
I'd like to open a bug regarding the Apache connector. We first ran into it back in 7.0 and I just confirmed today it still exists in 8.1 (at least Apache 2.0/win32).
The bug is that the connector only forwards bodies for a subset of HTTP methods, so Webdav, for instance, is unusable via the connector.
For instance, the ACL method, RFC 3744, when sent to apache looks similar to
--- snip --
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: close
<?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:">
<D:ace>
<D:principal>
<D:href>xxx</D:href>
</D:principal>
<D:grant>
<D:privilege> <D:read/> </D:privilege>
</D:grant>
</D:ace>
</D:acl>
but the BEA connector forwards this to BEA as:
-- snip---
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: Keep-Alive
WL-Proxy-SSL: false
WL-PATH-TRIM: /
WL-Proxy-Client-IP: 127.0.0.1
Proxy-Client-IP: 127.0.0.1
X-Forwarded-For: 127.0.0.1
X-WebLogic-Force-JVMID: unset
... which of course times out since the body is not sent but CL is (correctly) specified.
We have to ship our product with a separate apache module which changes all methods to a POST, then stuffs the real method in a header. Then in our special servlet that we ship just for BEA, we extract the real method from the header and use it instead of the POST in the ServletRequest.
Can someone with karma at BEA file this bug? Other methods with bodies that I suspect will probably fail include OPTIONS, PROPPATCH, & PROPFIND. I also verified that arbitrary (ie non-RFC'd) http methods will fail to transmit a body as well.
Our last customer who used our application with BEA was supposed to open a bug about this via standard support means but I don't have any record of it ever being done.
Thanks,
Keith