#1015 Reject unknown user actions instead of silently returning 200 Pull request opened by mehdi-shokohi UserActionHandler switches on the {action} path segment but had no default case. An unrecognized action (e.g. "update") matched none of add/edit/remove, skipped every branch, and still fell through to the trailing HTTPResponse — returning 200 {"data":""} while creating, editing, or removing nothing. Callers reasonably read the 200 as success, so a typo'd action silently no-ops. Add a default case that returns 400 "invalid action". jmpsec/osctrl