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

SchemaGenerator is not using the SCRIPT_NAME in the url #4305

Closed
6 tasks done
bobkarreman opened this issue Jul 25, 2016 · 0 comments
Closed
6 tasks done

SchemaGenerator is not using the SCRIPT_NAME in the url #4305

bobkarreman opened this issue Jul 25, 2016 · 0 comments

Comments

@bobkarreman
Copy link

bobkarreman commented Jul 25, 2016

Checklist

  • 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

Deploy your django project on a subpath with a proxy and make sure to set the SCRIPT_NAME header.

Expected behavior

Urls in the schema to be using the URLs with the SCRIPT_NAME prepended.

Actual behavior

URLs without the SCRIPT_NAME making the Django REST Swagger UI unusable, since its calling to the wrong URLs.

Also see this ticket at the Django REST Swagger repo: marcgibbons/django-rest-swagger#494 (comment)

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

No branches or pull requests

2 participants