-
|
Hello again, I currently run into another issue, where I am a bit lost, and hope for some guidance here. Currently I am generating my client code with quarkus-cxf But now when I try to start a request, I get the following Error: I already tried a lot of things like explicitly set the encoding on the request: Unfortunately this doesn't help. I also did not find any other threads/docs/infos about this problem. Does anybody has an idea what can cause this error? Is it something on client side or something on server side? Is there a possibility to extend the logging to get more information? (if this is not the right place to ask this question, would you please be so kind to point me into the right direction.) Thank you very much in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
|
After checking again, this seems to be caused not by the message sending, but by the server response. It is caused by this line of code of String normalizedEncoding = HttpHeaderHelper.mapCharset(charset);
if (normalizedEncoding == null) {
String m = new org.apache.cxf.common.i18n.Message("INVALID_ENCODING_MSG",
LOG, charset).toString();
LOG.log(Level.WARNING, m);
throw new IOException(m);
}This line of code can only be reached if there is a charset provided but it is not really parsable. Unfortunately, the LoggingFeature does not log the Response if it comes to this error. |
Beta Was this translation helpful? Give feedback.
-
Could you perhaps attach a Java debugger and set a breakpoint in the code above to see the value of |
Beta Was this translation helpful? Give feedback.
-
|
Ok thanks for the hint. Had to compile in jvm mode first but now i can debug it like a charm Thanks again for the hint. Now I have to contact the team which provides this service. 🚀 Or is there a way to intecept the response before it gets there and eliminate duplicate headers on our side? (would make my life easier) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for finding the root cause, @Framus! |
Beta Was this translation helpful? Give feedback.
-
|
They fixed it on their side. |
Beta Was this translation helpful? Give feedback.
Ok thanks for the hint. Had to compile in jvm mode first but now i can debug it like a charm
The service seems to send an invalid Content type :
text/xml; charset=utf-8,text/xml; charset=utf-8or better to say duplicates the header and therefore it gets invalid. This leads to an extraction to this encodingutf-8,text/xmlwhich is indeed invalid.Thanks again for the hint. Now I have to contact the team which provides this service. 🚀
Or is there a way to intecept the response before it gets there and eliminate duplicate headers on our side? (would make my life easier)