I don’t think it would be relevant. I moved the topic to the v1 category, because it looks like v1 code.
I do fear, however, that you may have elided the problem away in your redaction for posting. As you have written it here, the url you are attempting to reach seems like it would look something like “LINK3.0&job=Search&session=abc123”. That’s not a valid URL: it’s missing a protocol and host at the beginning, which is where I suspect the problem lies.
“localhost” as a host name is particularly problematic and prone to causing symptoms such as the one you describe, as well as having devices and development machines on different networks. So my advice is to concentrate on the hostname part of the URL (which I’m not seeing here). The problem as you describe it is that the device is not properly resolving that hostname.