[
https://issues.jboss.org/browse/WFLY-2699?page=com.atlassian.jira.plugin....
]
Stuart Douglas commented on WFLY-2699:
--------------------------------------
I think I know what may be causing this. Is there any chance that liferay is setting
both:
Transfer-Encoding: chunked
Content-Length: x
headers?
It looks like Undertow does not handle this situation correctly, according to the RFC in
this case the content-length should be ignored, which Undertow is not doing. I will fix
upstream, which will hopefully resolve the issue.
liferay portal does not work
----------------------------
Key: WFLY-2699
URL:
https://issues.jboss.org/browse/WFLY-2699
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: MichaĆ Zegan
Assignee: Stuart Douglas
Hello.
I have commpiled the full wildfly package and set gerrit, jenkins, and the nexus repo
manager on it, all works perfectly.
The problem:
I tried to deploy liferay on the same instance.
I did everything and then deployed the webapp.
The deploy was successful, but it didn't work.
I have the appserver behind apache reverse proxy, trying to load a page displays error
502 proxy error.
I checked with telnet what happens by telnetting to the backend appserver and sending a
GET request for /.
The response was incorrect, I got the expected document but without the status line and
headers, that makes it clear why apache sait error 502.
Liferay probably works with jboss as 7 and tomcat/etc, so I think undertow must have
something to do with it
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira