AW: Change target endpoint of generated stub

Was (of course) my fault ;) All ok, setTargetEPR does work as expected. Sorry for the noise ... -Ursprüngliche Nachricht- Von: Clemens Wyss DEV [mailto:[email protected]] Gesendet: Donnerstag, 24. November 2016 08:33 An: '[email protected]' Betreff: Change target endpoint of

Re[6]: HTTP :unsupported content-encoding of '' found

I followed the answers from the server fo a few days and found that sometimes the server sends no Content-Encoding and I still get this error - "HTTP :unsupported content-encoding of ''". Down there is a header received from the server with this error and without Content-Encoding. Why is Axis as

Re: Re[6]: HTTP :unsupported content-encoding of '' found

On Thu, Nov 24, 2016 at 8:43 PM, Sterpu Victor wrote: > I followed the answers from the server fo a few days and found that > sometimes the server sends no Content-Encoding and I still get this error - > "HTTP :unsupported content-encoding of ''". I doubt that. If that was the case, then Axis2 wo

Re[8]: HTTP :unsupported content-encoding of '' found

This heappens in isolated cases, in thye last 5 days I have 14 such errors out of 900 SOAP calls. This is not a Axis2 problem, http client 3 has the problem and is somehow triggered by this weird header and content received from the server. I mean all the majority of the response headers that ca