Uploaded image for project: 'Velocity Tools'
  1. Velocity Tools
  2. VELTOOLS-115

Improve exception and HTTP error management

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0
    • Component/s: VelocityView
    • Labels:
      None
    • Environment:
      Servlet container

      Description

      Currently the exception management and missing resources are not satisfactory.
      In particular:
      1. if an exception happen during rendering a template, an exception stack trace is put inside the result, with an HTTP 200 code;
      2. if a resource is missing, but it is intercepted by the VelocityViewServlet, it renders with a page with HTTP 200.

      It should be:
      1. HTTP 500 with error page. If it is not possible (if the response is committed), the error page should be included.
      2. HTTP 404 with error page.
      In both cases the configuration of the webapp should be considered.

        Attachments

        1. veltools-exception.diff
          6 kB
          Antonio Petrelli
        2. veltools-exception.diff
          3 kB
          Antonio Petrelli

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              brenmcguire Antonio Petrelli
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: