Project

General

Profile

Actions

Bug #33787

closed

Drop non-standard compliant way of selecting api version

Added by Tomer Brisker over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
API
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

We currently allow passing the api version using a version string in the Accept: HTTP header. This is not compliant with the HTTP standard and is not actually needed since we currently only have one API version and no plans to add v3 in the foreseeable future.

Actions #1

Updated by The Foreman Bot over 2 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Tomer Brisker
  • Pull request https://github.com/theforeman/foreman/pull/8877 added
Actions #2

Updated by The Foreman Bot over 2 years ago

  • Fixed in Releases 3.1.0 added
Actions #3

Updated by Tomer Brisker over 2 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF