Bug #4800
closed
Latest API prefix is not correct
Added by Vincent MEMBRÉ over 10 years ago.
Updated about 10 years ago.
Description
URLs on latest API in 2.9 are waiting for prefix "lastest" instead of "latest"...
This is not happening in 2.10 because of the refactoring on how we create API ...
- Subject changed from typo in latest API URL only in 2.9 to in 2.9, you cannot access latest API using "latest" prefix (use lastest instead ...)
- Status changed from New to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/505
Great the doc didn't had the typo, else we would have been in a big mess to support it.
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Subject changed from in 2.9, you cannot access latest API using "latest" prefix (use lastest instead ...) to Latest API prefix is not correct
- Status changed from Pending release to Released
Also available in: Atom
PDF