Project

General

Profile

Actions
Copy link

Bug #10939

closed

Features list doesn't reflect availability per protocol

Added by Dominic Cleal about 9 years ago. Updated about 5 years ago.

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

Description

If I set up a smart proxy with most modules enabled on HTTPS, but one module enabled on both and request /features on HTTP (or add it to Foreman), then the smart proxy advertises the union of all features irrespective of the protocol it's available on.

Perhaps /features should only list those enabled on the current protocol?

Related issues 1 (0 open — 1 closed)

Related to Foreman - Bug #12655: Foreman-Proxy not respecting config files in Resolved12/01/2015Actions
Actions
Copy link
 #1

Updated by Aaron Krzywicki over 8 years ago

  • Related to Bug #12655: Foreman-Proxy not respecting config files in added
Actions
Copy link
 #2

Updated by Ewoud Kohl van Wijngaarden about 5 years ago

  • Status changed from New to Resolved

With the /v2/features endpoint we do expose the HTTP/HTTPS availability.

Actions
Copy link

Also available in: Atom PDF