503 instead of page not found when entity with identity cannot be found
Previously, an URL with outdated
id
of an entity was redirected to the page not found-page.
This has changed since changes to transaction retries/page cache. It now redirects to a 503 page with escaped HTMLTrace when 503 is shown while 404 is expected:
Submitted by Elmer van Chastelet on 2 March 2016 at 12:49at webdsl.generated.templates.TrackPage.loadArguments(TrackPage.java:193) at webdsl.generated.templates.TrackPage.initVarsAndArgs(TrackPage.java:41) at utils.AbstractPageServlet.serve(AbstractPageServlet.java:109) at utils.DispatchServletHelper.handlePage(DispatchServletHelper.java:861) at utils.DispatchServletHelper.doServe(DispatchServletHelper.java:807) at utils.DispatchServlet.doGet(DispatchServlet.java:417) at javax.servlet.http.HttpServlet.service(HttpServlet.java:618) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
Issue Log
On 8 April 2016 at 11:50 Danny Groenewegen commented:
https://github.com/webdsl/webdsl/commit/14ae01560126dec102517483136d6df44c99411a
On 8 April 2016 at 11:50 Danny Groenewegen closed this issue.
Log in to post comments