Bug 794051 (JBEPP-1119)

Summary: Unsucessful login page is not displayed when using Apache with mod_jk
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: William Antônio <wsiqueir>
Component: PortalAssignee: hfnukal <hfnukal>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.GACC: epp-bugs, mposolda, theute, wsiqueir
Target Milestone: ---   
Target Release: 5.2.0.CR01   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1119
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
mod_jk Apache
Last Closed: 2011-11-14 23:05:51 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description William Antônio 2011-08-24 14:48:45 UTC
Complexity: Low
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007rJQ5
project_key: JBEPP

When you unsuccessful try to login to EPP with Apache in front of it, balanced with mod_jk, you will be redirected to login.jsp page, but the content-type of header is text/plain, so the page is not rendered properly. This is due the URL:

http://{host}/portal/private/j_security_check?j_username=abc&j_password=rememberme-1248940447

If you add some extension after j_security_check, for example .html, the page will be correctly rendered.

I'm aware it's not a portal issue, it's something from Apache side:
- directly access portal we do not face this problem;
- portal's login.jsp page sets the content type to text/html;

But I would like to suggest some solution to avoid it.

Our current workaround is to create a URL Rewrite that will force the content type of the login page:

RewriteEngine on

#resolves j_security_check problem
RewriteRule /portal/private/j_security_check - [T=text/html]

Comment 4 mposolda 2011-11-13 23:32:00 UTC
yes, it's duplication of JBEPP-966. EPP need to return header "Content-type" in all HTTP responses, otherwise Apache will treat is as text/plain (if not reconfigured).

I've just found that it's still the issue in EPP 5.2. It seems that JBEPP-966 has been fixed only in EPP 5.1.1 but not in 5.2 branch. In EPP 5.2 is the fix missing in ErrorLoginServlet .

Comment 5 hfnukal@redhat.com 2011-11-14 23:05:51 UTC
Release Notes Docs Status: Added: Not Required