-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Working Group Meeting Minutes – January 28th, 2022
Bill McDonald edited this page Feb 11, 2022
·
2 revisions
cmi5 Working Group Meeting Minutes – January 28th, 2022
Attendees
Notes
The group discussed the following Catapult issue regarding HTTP Status Codes : https://github.com/adlnet/CATAPULT/pull/30
The Catapult team asked the group to review the issue and it was generally agreed that the approach used what correct.
How Catapult is handling HTTP errors:
- 403 rejections by default
- 401’s if no valid credentials
- 401/403 (outside of session)
- 400 – bad actor,
- 500 – Error codes
Best Practices for error handling
- What should an AU do?
- UI/Message
- Error codes
What should an LMS do?
- UI/Message
- Error codes
How HTTP error codes are usually used ....
- 401 = Not Authorized
- 400 = bad xAPI format
- 403 = Statement that violates cmi5 rules.
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub:
http://aicc.github.io/CMI-5_Spec_Current/