[MGNLWLS-14] Make Magnolia compatible with Weblogic standard contextPath URIs Created: 06/Aug/15  Updated: 25/Oct/18  Resolved: 18/Aug/15

Status: Closed
Project: Oracle WebLogic Compatibility
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.1

Type: Improvement Priority: Major
Reporter: Edwin Guilbert Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: support, weblogic
Remaining Estimate: 0.5d
Time Spent: 0.5d
Original Estimate: 1d
Environment:

Weblogic 12c Magnolia 5.3.9


Issue Links:
Relates
causality
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: Sprint 6 (Kromeriz)
Story Points: 1

 Description   

Magnolia isn't prepared for URIs containing just the contextPath without a slash "/" at the end.

For example, if you enter:

http://magnoliaAuthor/

You get redirected to login page.

But if it lacks the slash:

http://magnoliaAuthor

You don't get redirected.

Same issue with site's domain mapping and so on. This issue has only been found in Weblogic 12c installations.



 Comments   
Comment by Edwin Guilbert [ 10/Aug/15 ]

Committed to master branch

Comment by Milan Divilek [ 17/Aug/15 ]

Reopen: With the patch If page name starts with context path then context path is removed twice.

Example:
Context path: /magnoliaAuthor
Page name: magnoliaAuthorBlaBlaBla
Then url to page is http://localhost:7001/magnoliaAuthor/magnoliaAuthorBlaBlaBla

So correct URI should be "/magnoliaAuthorBlaBlaBla", but instead of it it's just "BlaBlaBla"

Comment by Edwin Guilbert [ 18/Aug/15 ]

I tested this patch and its still failing if you create a page with the contextPath as name and also create a subpage below.

For example:
Context path: /magnoliaAuthor
Page name: magnoliaAuthor
Subpage name: magnoliaAuthor/test

If you try to go to http://localhost:7001/magnoliaAuthor/magnoliaAuthor/test it gives 404.

This is not an issue introduced by this patch. With the current version of the module (2.0), it also happens. Maybe https://jira.magnolia-cms.com/browse/MAGNOLIA-2064 needs to be reopened?

Comment by Edwin Guilbert [ 18/Aug/15 ]

This is also happening to Magnolia 5.3.9 Enterprise on Tomcat (Community version works). So its not specifically related to this issue.

Created a bug for this issue: https://jira.magnolia-cms.com/browse/MAGNOLIA-6344

Generated at Mon Feb 12 10:24:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.