danielfernandez
commented
6 years ago There seems to be an error either accessing or processing your error.html page. At first sight I'd go more for the former, but anyway, the problem is that, as the template cache is disabled, the processing of the template takes part during its own parsing, and AttoParser's and Thymeleaf's error reporting get mangled a bit (besides, line and col information can be lost in some situations, see #191).
At first sight your template looks OK to me (except I have only limited knowledge of the Layout Dialect syntax, so I wouldn't be able to tell if your layout:* attributes are OK). So I'd propose you to first get rid of all the clutter caused by mixed AttoParser and Thymeleaf error reporting by enabling template cache.
This is something you can do from your application.properties file (or the equivalent file/mechanism you are using in your app) and setting spring.thymeleaf.cache=true. This way execution will happen from template models cached in memory and AttoParser will not be in the way (unless the error is that your template cannot be found, in which case it will still be AttoParser who will complain).
So please, could you enable that property, try again, and paste your new exception trace?
ConfuserConfidence
I'm facing a problem with Integration of Thymeleaf 3.0.10 and Spring Boot 2.0.6 version. I'm trying to handle my view errors with ErrorController. My ErrorController class handles the error and returning custom error page. But i'm getting NestedExceptions from other page which have an error. Am I missing any other configurations here. https://stackoverflow.com/questions/53039513/spring-boot-2-thymeleaf-3-0-10-exception-handling-not-able-to-return-error-htm Thanks in advance.