Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
H hublot
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • LINAGORA
    • LLGS
  • Labs
  • hublot
  • Issues
  • #22

Closed
Open
Created Jun 13, 2017 by Tom JORQUERA@tjorqueraContributor

hublot require allowing to run insecure content

Due to the fact that some of the external services do not expose secured (aka https, wss) end points, we need to configure our browser runner to allow access to insecure content.

This should not cause a problem in practice, but is still bad. We should ensure that this will not be needed in the future, by adding a secure endpoint to all external services.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking