To see if the server is listening on a given port, use telnet <servername> <portnumber>
You should get some kind of response within a reasonable period of time. If you know the IP of the server use that instead of the name and you can avoid DNS latency. Ping will only tell you if the server is on and accessible. As far as page not found, I don't think there is an easy way to check if a page is *going* to be available before you go there. But if the server is listening on the correct port, but no delivering pages, the issue is internal with the server, hence the error codes. Bob S > On Jun 26, 2018, at 08:02 , Sannyasin Brahmanathaswami via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Our app has contains content "in the package" and content streamed from "the > cloud" > > It’s a bit new to me dealing with TsNet, latency issues, timeout, and to give > the user feedback on status… it's a challenge…So 1 question at a time: > > How do you determine that a URL is not available *before* you set a [player > object, stream the text, show a slide, pick a YouTube etc]? > > One could obvious ping it and test for "404 page not found" , but the server > may respond with any number of messages. Rather than checking all those, in > there is way to do this? > > put exists(sRemoteURL) into sRemoteURLAvailable > return sRemoteURLAvailable > > So if it return "true" ; you can proceed with operations? If not, inform > user... > > Is there a header that you would get, if the URL were available? > > BR > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
