Troubleshooting
Problem
If you upload a theme and also an extension that calls a CSS file upon log in, the CSS file fails to load and a 441 unauthorized error appears.
Cause
The 441 unauthorized error occurs because the logon has not completed yet. Any request to static resources (for example, a CSS file) that comes from an extension is validated against an authentication filter. If you are not logged in at the time of the request, the response is 441. This is why you see the 441 error for the uploaded CSS in a login page extension. There is one exception to this rule: any file placed under a folder named login is ignored by the authentication filter.
Resolving The Problem
Temporary workaround
To work around this issue during your current session, you must manually reload the extension after you successfully log on.
Permanent solution
There are two ways to create login extensions that do not cause a 441 error:
- Place the CSS file in a folder called login (or in a subfolder in the login folder). Any file placed in a folder named login is ignored by the authentication filter. You can see an example of this file structure in the samples SampleLogin.zip and SampleLoginMultiple.zip
- Exclude the feature containing the CSS for the login perspective in your extension. For example, in spec.json, define an extension for login that excludes the feature containing the one calling the CSS:
{
"name":"cssOnly",
"schemaVersion": "1.0",
"extensions": [{
"perspective": "common",
"features": [{
"id": "com.ibm.samples.cssonly",
"cssStyles": [
"v1/ext/cssOnly/css/forallbutlogin.css"
],
"toolItems": []
}]
},{
"perspective": "common",
"features": [{
"id": "com.ibm.samples.cssonlyforall",
"cssStyles": [
"v1/ext/cssOnly/login/css/forall.css"
],
"toolItems": []
}]
},{
"perspective": "login",
"type": "login",
"features": [{
"id": "com.ibm.samples.excludes",
"excludeFeatures": [
"com.ibm.samples.cssonly"
],
"toolItems": []
}]
}]
}
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22016393