-
1. Re: always sending content-type text/html header
jaikiran May 23, 2016 12:35 AM (in response to caarlos0)I remember there was a similar issue discussed long back in these forums. Can't find that thread now. Can you try upgrading to WildFly 10.0.0.Final Downloads · WildFly and see if it's fixed there?
-
2. Re: always sending content-type text/html header
caarlos0 May 23, 2016 8:18 AM (in response to jaikiran)I looked into the issues and didn't found any like this one. Do you have the URL for it?
Unfortunately I can't upgrade to wildfly 10 as our app is still JDK7 for now.
-
3. Re: always sending content-type text/html header
jaikiran May 24, 2016 12:01 AM (in response to caarlos0)Carlos Alexandro Becker wrote:
Unfortunately I can't upgrade to wildfly 10 as our app is still JDK7 for now.
You probably already know this, but, you can run a Java 7 compiled application in a Java 8 runtime. Of course, there could be other considerations around your use case, so consider this as a FYI.
-
4. Re: always sending content-type text/html header
jaikiran May 24, 2016 12:46 AM (in response to caarlos0)Can you paste the jsp (or better still, attach a simple application) that reproduces this and also the kind of "assets" it uses? By the way, which OS is this running on?
-
5. Re: always sending content-type text/html header
caarlos0 May 24, 2016 9:59 AM (in response to jaikiran)I'm trying to make an app to reproduce the issue, but since I don't know exactly where the problem is, it might take a while.
OS X 10.11.5 Beta, also tested on ubuntu 14.04, both in both oracle jdk7 and 8.
-
6. Re: always sending content-type text/html header
caarlos0 May 24, 2016 6:49 PM (in response to caarlos0)I found the error.
We have an internal framework (yeah, I know), developed by a former architect, and the framework was declaring a `@WebFilter("/*")` and changing all requests' content-types.
I guess Jboss AS mime-type filter were running after that crappy stuff, and fixing it's mistakes, and undertow's filter is probably running earlier, causing the broken requests.
Either way, I fixed that thing and now it's working.
Sorry for the trouble caused here, I had check that framework before and somehow missed that part.
Now I'm fighting against security domains :/ Wildfly 9 security domains won't work