Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schema generation view (result of get_schema_view) returns HTTP 404 when some permission class raises Http404 #4645

6 tasks done
apragacz opened this issue Nov 2, 2016 · 3 comments


Copy link

apragacz commented Nov 2, 2016

I found this bug when I was using django-rest-swagger, but during debugging I found out that the problem is in the DRF itself.


  • I have verified that that issue exists against the master branch of Django REST framework.
  • I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
  • This is not a usage question. (Those should be directed to the discussion group instead.)
  • This cannot be dealt with as a third party library. (We prefer new functionality to be in the form of third party libraries where possible.)
  • I have reduced the issue to the simplest possible case.
  • I have included a failing test as a pull request. (If you are unable to do so we can still accept the issue.)

Steps to reproduce

  • Use a ViewSet with DRF permission class raising Http404, for instance DjangoObjectPermissions from rest_framework.permissions
  • Install django-rest-swagger in your django project
  • Go to the URL where swagger view is configured to be called

Expected behavior

The page loads and you can see all accessible endpoints.

Actual behavior

The page loads but you see message like this: "Can't read swagger JSON from http://localhost:8000/?format=openapi". When you check in the developer console you notice that this URL returned HTTP 404.

Copy link

tomchristie commented Nov 2, 2016

Closed via #4646

@tomchristie tomchristie added the Bug label Nov 2, 2016
@tomchristie tomchristie added this to the 3.5.3 Release milestone Nov 2, 2016
Copy link

glarrain commented Nov 29, 2016


Closed via #4645

You probably meant #4646

Copy link

tomchristie commented Nov 30, 2016

Thanks, yes - have now updated the comment!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

3 participants