ION NM fails to handle hex string with blank space

[d-linko]

When the ANMS sends to ION a hex sequence that contains a blank space, e.g. 0xc11541050502252381871819410000 (space at the end) the result is a log message from docker exec ion-manager journalctl --unit ion-nm-mgr --since today similar to:

Mar 17 14:42:27 ion-manager nm_mgr[77]: [nm/shared/utils/utils.c:193] x utils_atox x Non-hex character:
Mar 17 14:42:27 ion-manager nm_mgr[77]: [nm/shared/utils/utils.c:407] x utils_string_to_hex Can't AtoX 0 .

[BrianSipos]

There is a manager patch which will avoid this issue and will allow multiple controls to be present in one HTTP body. The specific change to nm_rest.c was made in dtnma-tools repo and can be added to ANMS ION as a patch.