Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-21955

Access to restricted content results in error 500

    XMLWordPrintable

    Details

      Description

      When a user attempts to access content that he has no read access to, an error 500 is thrown, instead of a 403. That makes it difficult for developers to implement a custom handler for access denied situations.

      Steps to reproduce:
      • Create a folder in the back end
      • Open it, as anonymous, in the front end
      • Switch it to restricted section
      • Refresh the front end page
        => expected result: a 403 exception
        => actual result: 500 exception

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                joaquim.cavalleri-obsolete@ez.no Joaquim Cavalleri (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days
                  2d