which port is beeing used with get URL?
bobsneidar at iotecdigital.com
Fri May 19 18:11:35 CEST 2017
You will never get this completely right. I go on customer networks all the live long day, and there are places where IT people seem more interested in preventing communication than enabling it. Also, as mentioned, some anti-malware software is horrible. One particular one was preventing a user from printing to a brand new copier from his Windows 10 desktop. I was pulling my hair out trying to figure it out, then I said, "Just for kicks and grins, let's disable your AV software." Worked a peach.
> On May 19, 2017, at 02:00 , Mark Waddingham via use-livecode <use-livecode at lists.runrev.com> wrote:
> On 2017-05-19 10:40, Tiemo Hollmann TB via use-livecode wrote:
>> Am I right, that using "put URL" is a standard http:// protocol via port
>> 8080? Or is there a special port being used by LC?
> HTTP is port 80 - HTTPS is port 443.
> LC does not do anything non-standard here (unless you specify, e.g. http://livecode.com:93).
>> Are there any ideas from your experience, what and how to check for to find
>> the blocking factor in a customer network?
> Right, so - we know there are problems with LiveCode's networking stack communicating in some network environments. However, the problem is that we're not sure what configurations are actually causing the problem.
> Trevor DeVore has done a lot of work over the years to help improve the internet settings auto-discovery, to make LiveCode much better in this regard; however, things still aren't perfect.
> If we can find a way to fetch all the info about places which are not letting libURL work, then we can look into making it work... The problem is working out how to collect that information.
> If anyone has any ideas on this score then that would be most helpful!
> Warmest Regards,
> Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
More information about the use-livecode