Am 2020-04-20 um 11:11 schrieb Rémy Maucherat:
On Mon, Apr 20, 2020 at 10:58 AM Michael Osipov <micha...@apache.org> wrote:
Am 2020-04-20 um 10:05 schrieb Mark Thomas:
On 18/04/2020 20:59, micha...@apache.org wrote:
This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a commit to branch 7.0.x
in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/7.0.x by this push:
new 08879ae Remove redundant sole path/URI from error page
message on SC_NOT_FOUND
08879ae is described below
commit 08879aeb5e30933bc0a6aaea6c1fa8a9ef4b8a58
Author: Michael Osipov <micha...@apache.org>
AuthorDate: Sat Apr 18 20:58:40 2020 +0200
Remove redundant sole path/URI from error page message on
SC_NOT_FOUND
When a component issues a SC_NOT_FOUND don't respond with the
path/URI only in
the error message because it does not offer any more detail about
the error,
plus the client knows the path/URI already.
Not necessarily. The client has no visibility of forwards or includes.
In a more complex application it might not be obvious that a forward /
include has occurred. Including the path for the resource that could not
be found makes debugging significantly easier.
For the dev likely, for the user still irrelevant. What about logging at
debug level for the dev to still be able to find issues (like in
SSIServlet)? At the end, only the dev cares about more context. WDYT?
I would also prefer keeping them. This way users can report a more useful
error.
What about a more descriptive message rather than the blunt path/URL?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
