Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #5445

Closed (moved)
(moved)
Open
Created Mar 22, 2012 by Karsten Loesing@karsten

Atlas doesn't handle Onionoo's HTTPS redirects correctly

After moving Onionoo to a host that provides HTTPS, or rather a host that enforces HTTPS by redirecting HTTP requests to HTTPS, Atlas has a problem: it doesn't handle HTTP 302 redirects correctly. It simply says "Backend error!" The problem goes away with HTTPS Everywhere enabled, because then the client rewrites the HTTP link to HTTPS. But without HTTPS Everywhere, the server sends a 302 and the client gets confused.

An easy fix is to replace the three HTTP URLs in Atlas' sources with HTTPS URLs. That's probably a good idea, regardless of the stated issue.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking