Message Title

No it is not fixed. If you use the attached index.html (as /idp.war/idex.html) you will get a really funny behavior:

You will see the contents of the index.html and then the contents of the hosted page.
This index.html even breaks SAML handling (I guess because it is too big and forces the response to be committed).
Here is the exception you will get:

22:27:09,765 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
22:27:09,766 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started (with errors) in 2498ms - Started 344 of
 383 services (1 services failed or missing dependencies, 68 services are lazy, passive or on-demand)
22:32:12,918 ERROR [org.picketlink.common] (http-/127.0.0.1:8080-3) Unexpected error: java.lang.IllegalStateException: JBWEB000029: Cannot reset buffer after respons
e has been committed
        at org.apache.catalina.connector.Response.resetBuffer(Response.java:694) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
        at org.picketlink.identity.federation.web.util.PostBindingUtil.sendPost(PostBindingUtil.java:144) [picketlink-federation-2.7.0.Beta2.jar:]
        at org.picketlink.identity.federation.web.util.IDPWebRequestUtil.send(IDPWebRequestUtil.java:236) [picketlink-federation-2.7.0.Beta2.jar:]
        at org.picketlink.identity.federation.bindings.tomcat.idp.AbstractIDPValve.processSAMLRequestMessage(AbstractIDPValve.java:993) [picketlink-jbas7-2.7.0.Beta2
.jar:2.7.0.Beta2]
        at org.picketlink.identity.federation.bindings.tomcat.idp.AbstractIDPValve.handleSAMLMessage(AbstractIDPValve.java:491) [picketlink-jbas7-2.7.0.Beta2.jar:2.7
.0.Beta2]
        at org.picketlink.identity.federation.bindings.tomcat.idp.AbstractIDPValve.invoke(AbstractIDPValve.java:405) [picketlink-jbas7-2.7.0.Beta2.jar:2.7.0.Beta2]
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
        at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.F
inal-redhat-19]
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
        at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]