Uploaded image for project: '[Read Only] - Hippo Essentials'
  1. [Read Only] - Hippo Essentials
  2. ESSENTIALS-471

Extend handling of non-found situation in CommonComponent

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • High
    • Resolution: Fixed
    • 1.02.04
    • 1.02.05
    • Component Library
    • None

    Description

      The current way of dealing with a bean-not-found situation is setting the status to 302 (which is a Found actually) and redirecting to some other url (e.g. /not-found).
      Another scenario we definitely need is the option to set the status to 404 and keep the visitor on the same URL. The content of some document should be shown there.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bleunis Bert Leunis (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: