[ 
https://issues.apache.org/jira/browse/CXF-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992026#comment-12992026
 ] 

Jason Downey edited comment on CXF-3304 at 2/8/11 4:27 PM:
-----------------------------------------------------------

As long as the HttpConduit was previously initialized, the workaround was fine. 
For the very first WebClient request, I found that I needed to manually 
register the ClientOnlyHTTPTransportFactory.

I've uploaded the final demo file illustrating this workaround.

      was (Author: jadowney):
    Final file illustrating workaround.
  
> WebClient POST to a resource that returns 401 returns a blank InputStream 
> when there's supposed to be text
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-3304
>                 URL: https://issues.apache.org/jira/browse/CXF-3304
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.3.2
>         Environment: JDK 1.6
>            Reporter: Jason Downey
>            Priority: Minor
>             Fix For: 2.3.3
>
>         Attachments: WebClientTest.java, cxf_jax_rs_post_401_bug.zip, 
> cxf_jax_rs_post_401_bug_httpurlconnection.zip
>
>
> I have two methods that return the same error message upon POST. The only 
> difference is that one returns a 404 response status, the other returns a 401 
> response status.
> POSTing to the resource that returns 404 returns an InputStream containing 
> the error message when you call Response.getEntity(). However, POSTing to the 
> resource that returns 401 returns a blank InputStream when you call 
> Response.getEntity().
> This problem was not reproducible with GET.
> Test case code attached. Launch the server using JettyServer. Then run the 
> WebClient test in WebClientTest.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to