I have some content that the download now as action script fails on a small % of clients. It’s a BAD SERVERNAME winsock -6 error. If the command fails, it stops the whole action. I know it’s an issue on the client.
That said, I would still like to do some error handling and deal with it myself. A sort of “On Error Resume Next” to coin a vbs phrase.
Since you are not using relay caching, that is probably the problem, but also the solution. If you don’t need relay caching, then use cURL or wget or Python or PowerShell or something else to download the file. You will then be able to continue on.
Another option is to just run another action if that one fails.
I guess. It’s actually hitting a webservice to populate some information. It is an appropriate use of the action. I guess I COULD deploy curl to the windows boxes. I think it might be available on a % of the linux boxes, but I can’t guarantee that.
I may put in a PMR for this one. I just want a consistent/standard way to do this for all clients, as opposed to just client side scripting it out.
I don’t deploy cURL to any endpoint. I just download it in the ActionScript, put it into the utility cache, use it, and then it gets deleted when the next thing runs.
See here: https://bigfix.me/fixlet/details/6048
If the BES Client is already using LibCURL then I could understand exposing that functionality in actionscript, and that would be useful.
cURL is exactly that. Load cURL in the actionscript, then everything is the same from there. You can use a prefetch block to only load cURL if not already available and only download the correct one for the OS in question.