Unable to get Http Header info in webservice Handler

Question

Hi,
I have been trying to get the Header info in my custom Handler unsuccessfully
for the past few days.
Upon web search, I am constantly redirected to use a Servlet filter to get the
headers. I have to use the Weblogic Native SOAP engine and not any Servlet Filters.
In Axis, I can do a (HttpServletRequest)messageContext.getProperty(HTTPConstants.MC_HTTP_SERVLETREQUEST)
which returns the HttpServletRequest and then I can get the headers off that.
I can't find something similar in WebLogic. Any ideas?
Any help in helping me track this problem down would be much appreciated.
Thanks,
Sridhar.

Answer 1

Yes, you are correct that you are taking a risk by using the "__BEA_PRIVATE_BINDING_PROP"
property, on the MessageContext object. The mechanism I provided is the recommended
(and supported) way to get the HTTP headers, as it only uses "documented" class.
Some developers think you are trying to "hide" something with undocumented classes,
but I don't think this is the case with BEA. There are good reasons and the point
you made about the likelihood of an unannouced future change breaking your code,
is probably pretty high on the list :-)
Getting the REMOTE_ADDR (or REMOTE_HOST) would most likely require the "undocumented"
approach you've taken. You could get the HttpServletRequest from this same HttpServerBinding
object, and call the getRemoteAddr() method on it. However, I really, really,
really think you should consult our "fantabulous" BEA support department, to see
if doing this will be supported.
Regards,
Mike Wooten
"Sridhar" <[email protected]> wrote:
>
Michael,
Thanks a bunch for your reply. I have been going crazy over this and
your reply
made my day.
I still have a slight problem with this though. This does not seem to
give me
the Client IP etc. Any ideas to get that?
Thanks again for the code. It was a great help.
Sridhar.
PS BTW, I found another way of getting the same info:
HttpServerBinding httpBinding = (HttpServerBinding) messageContext.getProperty("__BEA_PRIVATE_BINDING_PROP");
Enumeration headerEnum = httpBinding.getRequest().getHeaderNames();
while (headerEnum.hasMoreElements()) {
String header = (String) headerEnum.nextElement();
System.out.println("header = " + header);
System.out.println("header Value = " + httpBinding.getRequest().getHeader(header));
But, I am guessing BEA doesn't want me to go this route as they might
change the
implementation and my code will immediately break.
"Michael Wooten" <[email protected]> wrote:
Hi Sridhar,
You should be able to get at the HTTP Headers that were sent by theconsumer
of
your web service, by using the following code in your JAX-RPC handler:
import java.util.Iterator;
import javax.xml.rpc.handler.MessageContext;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.rpc.JAXRPCException;
import javax.xml.soap.MimeHeaders;
import javax.xml.soap.MimeHeader;
import javax.xml.soap.SOAPMessage;
public boolean handleRequest(MessageContext mc)
SOAPMessageContext messageContext = (SOAPMessageContext) mc;
try
SOAPMessage original = messageContext.getMessage();
MimeHeaders mimeheaders = original.getMimeHeaders();
MimeHeader mimeheader = null;
Iterator iter = mimeheaders.getAllHeaders();
for (; iter.hasNext();)
mimeheader = (MimeHeader) iter.next();
System.out.println("name=" + mimeheader.getName() + ", value="
+ mimeheader.getValue());
catch (Exception e)
e.printStackTrace();
throw new JAXRPCException(e);
Here's the output from the System.out.println():
name=Content-Type, value=text/xml
name=SOAPAction, value=""
name=User-Agent, value=Java1.4.1_05
name=Host, value=localhost:7001
name=Accept, value=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
name=Connection, value=Keep-Alive
name=Content-Length, value=505
Regards,
Mike Wooten
"Sridhar" <[email protected]> wrote:
Hi,
I have been trying to get the Header info in my custom Handler unsuccessfully
for the past few days.
Upon web search, I am constantly redirected to use a Servlet filterto
get the
headers. I have to use the Weblogic Native SOAP engine and not any
Servlet
Filters.
In Axis, I can do a (HttpServletRequest)messageContext.getProperty(HTTPConstants.MC_HTTP_SERVLETREQUEST)
which returns the HttpServletRequest and then I can get the headersoff
that.
I can't find something similar in WebLogic. Any ideas?
Any help in helping me track this problem down would be much appreciated.
Thanks,
Sridhar.