4 Replies Latest reply on Jul 17, 2018 6:47 AM by siva.ole

Wildfly 13.0.0.Final error UT005014: Failed to parse request: io.undertow.util.BadRequestException: UT000165: Invalid character ä in request-target

siva.ole Jul 14, 2018 6:08 AM

We have recently migrated and deployed our application.EAR (API's) packages in wildfly 13.0.0.Final from GlassFish 3 in Linux environment. While testing application api's its not supporting scandic characters and giving below error (Error copied from server.log from wildfly). But the same test request working fine with the application api's deployed in GlassFish server. I tried to study so many blogs related to wildfly but could not get any solutions. Could some one help here please.

I tired below setting changes in standalone.xml file to set the charset to UTF-8, but its not helped.

<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" url-charset="UTF-8"/> <servlet-container name="default" default-encoding="UTF-8">

2018-07-13 17:06:45,189 DEBUG [io.undertow.request.io] (default I/O-4) UT005014: Failed to parse request: io.undertow.util.BadRequestException: UT000165: Invalid character ä in request-target at io.undertow.server.protocol.http.HttpRequestParser.handleQueryParameters(HttpRequestParser.java:523) at io.undertow.server.protocol.http.HttpRequestParser.beginQueryParameters(HttpRequestParser.java:486) at io.undertow.server.protocol.http.HttpRequestParser.handlePath(HttpRequestParser.java:410) at io.undertow.server.protocol.http.HttpRequestParser.handle(HttpRequestParser.java:248) at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:187) at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136) at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:147) at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:93) at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:52) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291) at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:131) at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612) at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)

Below is the input request xml which we are sending both to Wildfly and GlassFish:

<SOAP-ENV:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP-ENV:Header>

<callbackLocation>http://TESTUI</callbackLocation>

</StartHeader>

</SOAP-ENV:Header>

<SOAP-ENV:Body>

<spec:searchItemList>

<spec:attribute>

<spec:name>district</spec:name>

<spec:value>Jär</spec:value>

</spec:attribute>

</spec:searchItemList>

<spec:attributeName>district</spec:attributeName>

<spec:maxItems>100</spec:maxItems>

</listAttributeValuesRequest>

</ListAttributeValues>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

1. Re: Wildfly 13.0.0.Final error UT005014: Failed to parse request: io.undertow.util.BadRequestException: UT000165: Invalid character ä in request-target

jewellgm Jul 16, 2018 9:15 AM (in response to siva.ole)

I don't think it's the contents of your SOAP message that is the problem, but the URI that is used to touch the web service. You may want to try adding the following Java option to your startup script:

-Dorg.wildfly.undertow.ALLOW_UNESCAPED_CHARACTERS_IN_URL=true

Edit: I don't have Wildfly 13 downloaded to verify, but it looks like you can set the "allow-unescaped-characters-in-url" flag in the undertow subsystem. I think these options were added as part of the undertow:6.0 schema as attributes of the https-listener and http-listener elements.

See here:
wildfly/wildfly-undertow_6_0.xsd at master · wildfly/wildfly · GitHub

An example configuration:
wildfly/undertow-6.0.xml at master · wildfly/wildfly · GitHub
1 of 1 people found this helpful
Actions
2. Re: Wildfly 13.0.0.Final error UT005014: Failed to parse request: io.undertow.util.BadRequestException: UT000165: Invalid character ä in request-target

siva.ole Jul 17, 2018 6:47 AM (in response to jewellgm)

Hi Greg,

Thanks for you suggestions and help, I tried your suggestion by adding parameter allow-unescaped-characters-in-url="true" in standalone.xml based on GITHUB Example which you given, this time its not given the same error but wildfly converted the value into some illegal format. I am adding the request example below which I captured from the wildlfy logs. Could you please help me to suggest here.

Original value: Järv, wildfly converted this to: J�rv

<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" allow-unescaped-characters-in-url="true"/>
<https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true" allow-unescaped-characters-in-url="true"/>

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<StartHeader SOAP-ENV:actor="http://schemas.xmlsoap.org/soap/actor/next" SOAP-ENV:mustUnderstand="0" xmlns="http://www.openuri.org/2002/04/soap/conversation/">
<callbackLocation>http://TESTUI</callbackLocation>
</StartHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ListAttributeValues xmlns="http://www.openuri.org/" xmlns:v001="http://xml.comptel.com/NIMS/address/listAttribteValuesRequest/v002" xmlns:v0011="http://xml.comptel.com/NIMS/address/v002">
<listAttributeValuesRequest xsi:schemaLocation="http://xml.comptel.com/NIMS/address/listAttributeValuesRequest/v002 http://xml.comptel.com/NIMS/address/listAttributeValuesRequest/v002" xmlns="http://xml.comptel.com/NIMS/address/listAttributeValuesRequest/v002" xmlns:spec="http://xml.comptel.com/NIMS/address/v002" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<spec:searchItemList>
<spec:attribute>
<spec:name>district</spec:name>
<spec:value>J�rv</spec:value>
</spec:attribute>
</spec:searchItemList>
<spec:attributeName>district</spec:attributeName>
<spec:maxItems>100</spec:maxItems>
</listAttributeValuesRequest>
</ListAttributeValues>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Actions
3. Re: Wildfly 13.0.0.Final error UT005014: Failed to parse request: io.undertow.util.BadRequestException: UT000165: Invalid character ä in request-target

jewellgm Jul 17, 2018 10:31 AM (in response to jewellgm)

After looking at your SOAP message again, I saw the <spec:value> element which contains the character that is being complained about. I'm sorry that I missed it earlier -- it wasn't easy to see.

Since the error message you are getting comes from Undertow, I'd still suggest making that change above to see if that resolves the situation for you. Since it's part of the SOAP payload, there may also be an issue with CXF when it begins to process the message. One step at a time, though.
Actions
4. Re: Wildfly 13.0.0.Final error UT005014: Failed to parse request: io.undertow.util.BadRequestException: UT000165: Invalid character ä in request-target

siva.ole Jul 17, 2018 10:50 AM (in response to jewellgm)

Hi Greg,

Thanks for your quick suggestions, I managed to fix the problem by adding below to flags as attributes of the https-listener and http-listener elements in the undertow subsystem. Now my API working as expected.

<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true" allow-unescaped-characters-in-url="true" url-charset="windows-1252"/>

<https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true" allow-unescaped-characters-in-url="true" url-charset="windows-1252"/>
Actions

Go to original post