[MGNLWLS-10] Returned context path is incorrect for long URLs Created: 13/Nov/09 Updated: 26/Jun/15 Resolved: 26/Jun/15 |
|
| Status: | Closed |
| Project: | Oracle WebLogic Compatibility |
| Component/s: | None |
| Affects Version/s: | 1.2 |
| Fix Version/s: | 1.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Jan Haderka | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
In Weblogic 10.1 happens that when URL is longer then 150 characters and context path is short (4 characters), the context path returned by the request contains extra characters. |
| Comments |
| Comment by Magnolia International [ 13/Nov/09 ] |
|
reopening so we don't forget to check if WL allows "deep" contextpaths |
| Comment by Jan Haderka [ 13/Nov/09 ] |
|
Except weblogic fails to deploy the webapp with such a context path every time i tried. But you are right we should allow it.
Will also try to test on the latest and greatest weblogic version to see if the issue got fixed in the mean time or not. |