cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <>
Subject [jira] Closed: (CXF-1490) Need to trap "com.ctc.wstx.exc.WstxUnexpectedCharException" in ReadHeadersInterceptor and give HTML response message
Date Thu, 27 Mar 2008 01:09:24 GMT


Glen Mazza closed CXF-1490.

    Resolution: Fixed


> Need to trap "com.ctc.wstx.exc.WstxUnexpectedCharException" in ReadHeadersInterceptor
and give HTML response message
> --------------------------------------------------------------------------------------------------------------------
>                 Key: CXF-1490
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.1
>            Reporter: Glen Mazza
>            Priority: Minor
> If an HTML response in returned from the service to the client, due to a basic authentication
or other error, the following error stack is returned (if chunked transfer encoding is set
to FALSE for the HTTPConduit/client*):
>     [java] Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
'"' (code 34) in DOCTYPE declaration; expected a space between public and system identifiers
>      [java]  at [row,col {unknown-source}]: [1,55]
>      [java] 	at
>      [java] 	at
>      [java] 	at
>      [java] 	at
>      [java] 	at
>      [java] 	at
>      [java] 	at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(
>      [java] 	... 15 more
> This requires the user to go to Wireshark[1] to determine what the HTML error message
is.  I think it would be helpful for the user if this error was trapped, and the HTML error
message output to the client console as part of the exception, to save that step.
> Steps to duplicate:  Make an HTTPS client connection to a server with (a) wrong username
and/or password and (b) chunked transfer encoding set to false as shown here:
> <beans xmlns="" xmlns:xsi=""
xmlns:sec="" xmlns:http=""
>    <http:conduit name="{}MyPortName.http-conduit">
>    <http:authorization>
>      <sec:UserName>???</sec:UserName>
>      <sec:Password>???</sec:Password>
>    </http:authorization>
>    <http:tlsClientParameters secureSocketProtocol="SSL"/>
>    <http-conf:client AllowChunking="false"/>
>    </http:conduit>
> </beans>
> Running the client should produce the above error stack.
> [1]
> * if chunked transfer encoding is true, we get a HttpRetryException error message as
shown here:
this is not currently a concern for me.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message