Websocket based on ws code fixes needed
Budget: $10 – $30 USD
I have a custom websocket that is setup to enable server-side cli access from a connected front end app. There are 2 issues with the websocket.
(1) The websocket does not allow cli cmds that have multiple arguments like the one pictured or ....may ...cause an error...we need to know if this is causing an error and to have it fixed. Sample Argument sent over to cli: - screen -ls | egrep "^\s*[0-9]+.Lightning" | awk -F "." '{print $1}' | xargs kill
(2) When the front end app sends a cmd over the websocket and it fails we need the full verbose response as seen in the photo "cli full verbose". Currently, when sending cmds that fail over postman, we are returning simply "failed" as pictured in "postman pass fail" photo. We need the full vervose response returned in post over the websocket.
(1) The websocket does not allow cli cmds that have multiple arguments like the one pictured or ....may ...cause an error...we need to know if this is causing an error and to have it fixed. Sample Argument sent over to cli: - screen -ls | egrep "^\s*[0-9]+.Lightning" | awk -F "." '{print $1}' | xargs kill
(2) When the front end app sends a cmd over the websocket and it fails we need the full verbose response as seen in the photo "cli full verbose". Currently, when sending cmds that fail over postman, we are returning simply "failed" as pictured in "postman pass fail" photo. We need the full vervose response returned in post over the websocket.