Undertow (Wildfly8) doesn't handle request parameters as expected

[Qu Vad]

Hi

I do migration from Jboss AS7 /EAP6 to Wildfly8 and would like to ask here for any hint about undertow, why it doesn't handle request parameters as catalina does in EAP6.
So, I make a request from client to url './client/boom/index.htm?i=1', it comes to an error servlet where I want to get value of parameter i

httpServletRequest.getParameter("i");

With EAP6 it returns 1, but with Wildfly8 it return null. Why?

Additional info. I have a security domain called 'boom' declared in jboss-web.xml
<jboss-web> <security-domain>boom</security-domain> <disable-audit>true</disable-audit> </jboss-web>
and in standalone.xml
<subsystem xmlns="urn:jboss:domain:security:1.2"> <security-domains> ... <security-domain name="boom" cache-type="default"> <authentication> <login-module code="com.boom.security.BoomLoginModule" flag="required"/> </authentication> </security-domain> </security-domains> </subsystem>

Auth method is declared as basic in web.xml.

[Jaikiran Pai]

So, I make a request from client to url './client/boom/index.htm?i=1'

That appears to be a static htm file. Moreover that doesn't even look like the real URL. What exactly is the full URL and how is it mapped to the servlet in which you are invoking the getParameter API?

[Qu Vad]

Chain of calls is the following (assume basic auth):

1. Call with js to url './client/boom/index.htm?i=1'.
2. Flow doesn't come to subclass of UsernamePasswordLoginModule because authorization required.
3. Flow comes to the error-servlet with

httpServletRequest.getAttribute("javax.servlet.error.status_code") == 401
httpServletRequest.getAttribute("javax.servlet.error.message") == Unauthorized

Here, in the error-servlet I need to get parameter i. Error-servlet is mapped in this way:

<servlet-mapping>
    <servlet-name>error</servlet-name>
    <url-pattern>*.error</url-pattern>
</servlet-mapping>
...
<error-page>
    <error-code>401</error-code>
    <location>/Error.error</location>
</error-page>

[Jaikiran Pai]

So it looks like the request parameter isn't available in the servlet to which the control is passed after an error occurs. Although I haven't looked into the details/code, I suspect this might be related to this similar issue http://lists.jboss.org/pipermail/undertow-dev/2014-October/000975.html which got fixed in Undertow just a few days back. Someone from the Undertow development team will have to confirm that. Since you already have a thread in the JBoss developer community forums here https://developer.jboss.org/thread/249382, someone from the team will probably respond soon.

[Qu Vad]

Jaikiran Pai, thanks for hint. According to https://issues.jboss.org/browse/UNDERTOW-322 I replaced modules websockets-jsr, servlet and core of Undertow by the newest version 1.2.0-Beta1. It did not fix the issue.

[Jaikiran Pai]

That was just a guess, based on some details in that JIRA. So perhaps you are running into something else. I don't have the code right now, so can't help much further. Someone from the Undertow team might be able to help.

[Qu Vad]

Update. The list of attributes in error servlet is different in EAP6 and WF8

Attributes in WF8:

javax.servlet.error.message: Unauthorized
javax.servlet.error.status_code: 401
javax.servlet.error.servlet_name: default
javax.servlet.error.request_uri: /boom-portal/client/boom/index.htm

Attributes in EAP6:

javax.servlet.forward.request_uri: /boom-portal/client/boom/index.htm
javax.servlet.forward.context_path: /boom-portal
javax.servlet.forward.servlet_path: /client/boom/index.htm
javax.servlet.forward.path_info: /Error.error
javax.servlet.forward.query_string: i=1
javax.servlet.error.message:
javax.servlet.error.status_code: 401
javax.servlet.error.servlet_name: default
javax.servlet.error.request_uri: /boom-portal/client/boom/index.htm


Any idea why 'forward'-attributes are missing in WF8?

[Jaikiran Pai]

You might want to login to the IRC channel #wildfly as noted here http://wildfly.org/gethelp/ and point them to the discussion here. Usually you find some developers on that channel who are willing to help.

[Jaikiran Pai]

Just a FYI - Someone else ran into this problem today and raised it in the undertow-dev mailing list and it appears that this has been acknowledged as an open bug:

http://lists.jboss.org/pipermail/undertow-dev/2015-July/001298.html
https://issues.jboss.org/browse/UNDERTOW-505