We've installed the canned error handling application that comes with VE into the ODR. When accessing the error handler app directly, content is served properly - the only content really being a blue bar image and text saying what the error is.
The ODR has been configured to use the error application to handle errors. To test it out, the target application has been set to lazy start, so the error app gets invoked on first access to the target application.
The error application is running as it puts out the desired text and metatag refresh content, but the image is not being served properly. What's happening is that the context root isn't being changed to ErrorPageApp and the image can't be found.
Was wondering if anyone else has experienced this same issue and what they have done to get fix it. Does something need to be put in the Header options in the configuration?
Any help would be appreciated.
Pinned topic ODR: Custom Error Page problem
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2011-09-01T14:03:47Z at 2011-09-01T14:03:47Z by SystemAdmin
KeithS 060000MSV417 Posts
Re: ODR: Custom Error Page problem2011-08-26T18:16:21ZThis is the accepted answer. This is the accepted answer.Since the application that generates the HTTP error has a different context root than the error page application, when a browser renders the image in the error response, it tries to get the image from original application's context root. Try adding the a tag of the following form in the error page app response in the <Head> part of the html page:
<Base href="http://<Server>/<ErrorPageAppContextRoot>/" />
What you put for <Server> will depend on your topology but in most cases could be the ODR itself, which you can get from the servlet API. And of course replace <ErrorPageAppContextRoot> appropriately.
SystemAdmin 110000D4XK102 Posts
Re: ODR: Custom Error Page problem2011-09-01T14:03:47ZThis is the accepted answer. This is the accepted answer.
- KeithS 060000MSV4
Thanks for the response. I'll pass your suggestion along to the developer to see if they can make that quick fix and test it out.