Project

General

Profile

Actions
Copy link

Bug #7557

closed

websockets_encrypt setting is meaningless

Added by Stephen Benjamin about 10 years ago. Updated about 9 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Settings
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

If you set ':websockets_encrypt:' to false in /etc/foreman/settings.yml, it still starts the websockify proxy with SSL options. You also need to see :websockets_ssl_key: and :websockets_ssl_cert: to "" -- commenting them out is not sufficient either.

Related issues 1 (0 open — 1 closed)

Is duplicate of Foreman - Bug #9603: Setting called websockets_encrypt does not work correctlyClosedLukas Zapletal03/02/2015Actions
Actions
Copy link
 #1

Updated by Stephen Benjamin about 9 years ago

  • Is duplicate of Bug #9603: Setting called websockets_encrypt does not work correctly added
Actions
Copy link
 #2

Updated by Stephen Benjamin about 9 years ago

  • Status changed from New to Duplicate
Actions
Copy link

Also available in: Atom PDF