manageiq: Appliance-wide custom HTTP error pages
There is an open BZ for having the ManageIQ logo on the HTTP error (404, 422, 500) pages. The SUI team already implemented this feature in their project and I’m thinking about making it appliance-wide.
As we can not rely on the asset pipeline when using static error, I would like to move some minimal set of files from the SUI into the public folder of the main repo. When these files are in place, we can tell Apache to take over the error handling by using ProxyErrorOverride and ErrorDocument. However, this solves the errors for the classic UI only, for the SUI we might need some extra mod_rewrite configuration or some modifications in the Angular app.
The solution for the classic UI is super simple, the question is how much changes do we need for the SUI and if this is a good idea or not?
PS: we can always fall back and use the HTTP Status Cats API 🤣
About this issue
- Original URL
- State: open
- Created 7 years ago
- Comments: 28 (27 by maintainers)
@bdunne, @Fryguy, @carbonin : we really don’t want to have Rails serve the assets. That’s a step in the wrong direction for the UI.
This is a decision that has a significant impact on the UI and we need to be part of the discussion on this.
If you guys decide to have a separate httpd to do the auth, keep it slim etc. and move the assets out of that container, we would have to reintroduce Apache or some other http server in the UI container or in a seperate container just for the purpose of serving the assets.
Please, make sure that if you dig into things that have a potential of impacting the UI, you invide someone from the UI team to participate.
@bdunne it’s kinda strange to serve the assets with rails in general, but it’s possible with a conditional in the
config/routes.rb.