That is exactly the line I am referring to.
Simply replacing the call to res.setStatus with res.sendError would
definitely be wrong due to what you described. That change is not what I am
suggesting. It is simply what I did for a quick test. I was thinking it
would be worth it to add a flag as a s
2015-03-16 21:52 GMT+03:00 Jacob Haverkost :
> Version: 6.0.43
> OS: Win7 x64
>
> Currently, the CGIServlet does not appear to support using the 404
> error-page specified in the web.xml (ROOT). The error-pages work fine
>
> This appears to be due to the line, res.setStatus(404);, inside of doGet()
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jacob,
On 3/16/15 2:52 PM, Jacob Haverkost wrote:
> Version: 6.0.43 OS: Win7 x64
>
> Currently, the CGIServlet does not appear to support using the 404
> error-page specified in the web.xml (ROOT). The error-pages work
> fine
>
> This appears to
Version: 6.0.43
OS: Win7 x64
Currently, the CGIServlet does not appear to support using the 404
error-page specified in the web.xml (ROOT). The error-pages work fine
This appears to be due to the line, res.setStatus(404);, inside of doGet().
According to the documentation for HttpServletResponse.
