Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beat
  • beat.webbeat.web
  • Issues
  • #196

Closed
Open
Created Jun 02, 2015 by Laurent EL SHAFEY@laurent.el-shafey

Django-rest-swagger uses http scheme instead of https

On the production platform, the API documentation is available here. However, there is an issue with django-rest-swagger.

When clicking on the above mentioned documentation link, the address http://www.beat-eu.org/platform/docs/api-docs/ is shown instead of https://www.beat-eu.org/platform/docs/api-docs/, and the API documentation is not shown. If we manually update this address (to use https), then the API documentation shows up.

The suggestion of this issue is already applied in the Django's settings.py of the production server and this does not help.

Debugging at the javascript level, swagger submits a request with scheme set to http instead of https. Unfortunately, I've not found any way to force the use of https in django-rest-swagger.

Assignee
Assign to
Time tracking