[KULRICE-8440] 404 Error when accessing a KRAD page through the portal Created: 23/Oct/12  Updated: 24/Feb/14  Resolved: 23/Oct/12

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.2.0-rc1, 2.2
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Blocker
Reporter: Jerry Neal (Inactive) Assignee: Claus Niesen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
cloned from KULRICE-7208 Template Closed
relates to KFSOLD-27530 KFS is not working with IE 11 - retur... Closed
Similar issues:
KULRICE-7017When attempting to open DocumentOperation screen as an unauthorized user, you just get a 404 instead of an error screen
KULRICE-3137Several of the "Cancel" and "Close" buttons in the Portal result in 404 error.
KULRICE-5432Miscellaneous Kuali portal bugs related to accessibility
KULRICE-5849404 error for ui-bg_flat_75_ffffff_40x100.png
KULRICE-11426Ability to view KNS pages within the KRAD portal
KULRICE-11463On submit KRAD Docs don't return to the maint portal tab
KULRICE-5896Rice Dev: Error in Portal results in Frame Resizing Creep
KULRICE-10040KRAD Sample Application: Maintence doc displays. Route Log Section shows 404 Error.
KULRICE-5447KRAD application header/controls - persistence on page
KULRICE-9370404 when getting loading message on load of any KRAD view
Rice Module:
KAI Review Status: Not Required
KTI Review Status: Not Required


When accessing a page through the portal in env1, getting the following 404 error:

HTTP Status 404 - /kr-dev/rice-portal/scripts/easyXDM/resize_intermediate.html

type Status report

message /kr-dev/rice-portal/scripts/easyXDM/resize_intermediate.html

description The requested resource (/kr-dev/rice-portal/scripts/easyXDM/resize_intermediate.html) is not available.

Comment by Jerry Neal (Inactive) [ 23/Oct/12 ]

Hey Peter,

This is probably from the merge, maybe something got missed. Could we have Claus take a look and figure out the problem?


Comment by Peter Giles (Inactive) [ 23/Oct/12 ]

Hi Claus, can you take a look when you have a chance? SVN really didn't handle the conflict well, and I tried my best to clean it up but maybe I put the easyXDM content in the wrong place?

Comment by Claus Niesen [ 23/Oct/12 ]

I rolled back the easyXDM changes in trunk and Erik rebuilt the environment. So env1 is working again.

The issue is the application.contextname I was mentioning before. It's still an issue in the 2.1 branch (and env8). I'll be working on a solution now. BTW, EasyXDM testing with a stand alone server looks good so far.

Generated at Wed Apr 08 04:22:00 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.