Hi > In addition, I found out that the browser is also receiving the 400 status > code. > At minimum, due to expecting text/xml, when it gets a blank screen, it says > that it cannot parse it.
I don't think it is actually getting an empty 400, the fact CXF transport sets Content-Header should not cause that XML parsing error, you could use a tcpmon utility to confirm it (use say 8081 in your request URI and configure tcpmon to redirect from 8081 to 8080) Cheers, Sergey > > Here is the response to the browser, which was captured with a Firefox > plugin called Http Response Browser 0.3: > > http://pages.cs.wisc.edu/~zoerner/downloads/dev/samples/jaxrs_basic_http_demo/response.toBrowser.400_status > > https://addons.mozilla.org/en-US/firefox/addon/http-response-browser/ > > and here is what the response looks like when the browser prints a message > in response to it: > > http://pages.cs.wisc.edu/~zoerner/downloads/dev/samples/jaxrs_basic_http_demo/400_header_url_response_to_browser.png > > Have a great weekend also. > > Ryan > -- Sergey Beryozkin Application Integration Division of Talend http://sberyozkin.blogspot.com
