Forum Discussion
1 Reply
Sort By
- Michael_JenkinsCirrostratus
I've seen a few times where I've had similar problems that were related to DNS resolutions. So my Application URI for that resource wasn't accessible from the F5. You could take the Application and from within an SSH (I use Putty) session with the device, you can curl the URL and see if it works.
. (Or even try pinging the host name from the Application URI).curl http://example.com/heres/my/path
When you open a resource from the Webtop, your address bar should have that f5-w-XXXXX$$ part to it. If you want to check the host name, you can decode the XXXXX part. It's just a HEX encoding. That'll show you what the host it's trying to connect to on the back end.
Hope this helps in your case.