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

Access to restricted content results in error 500

    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

        Issue Links

          Activity

          Yannick Roger (Inactive) logged work - 18/Nov/13 3:23 PM
          • Time Spent:
            6 hours
             

            .

          Yannick Roger (Inactive) logged work - 19/Nov/13 1:00 AM
          • Time Spent:
            5 hours
             

            .

          Yannick Roger (Inactive) logged work - 20/Nov/13 4:24 PM
          • Time Spent:
            2 hours
             

            .

          Pedro Resende (Inactive) logged work - 21/Nov/13 12:22 PM - edited
          • Time Spent:
            3 hours
             

            Analyse and reproduce issue, write test case and verify the issue has been fixed

            People

            • Assignee:
              Unassigned
              Reporter:
              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