Re: Port designation in URL
Hi Jacque. In all IP communications, not only is the address the IP part, but there is also a port number associated with it. You don’t often see it because this information is added on later using the default port for whatever protocol. For instance, port 80 is the HTTP port. 21 and 22 is FTP. 465 is SSL and so forth. Now if you were to use another port, 81 for HTTP for example, you would have to explicitly put that in the URL: http://www.slylabs.com:81/support (That’s not a real URL btw so don’t click it.) There are a maximum number of usable ports, 65535 to be exact. The URL you have is obviously higher than that and BTW has a LETTER I in it! Yeah, that URL is bogus. Bob S On Dec 12, 2014, at 21:00 , J. Landman Gay jac...@hyperactivesw.commailto:jac...@hyperactivesw.com wrote: A little off topic, but does anyone know what the pipe means in a url in this format: www. domain.comhttp://domain.com/:443|6928 It's coming back in the error response from a POST request and the request times out. What does the second port number mean, if that's what it is? -- Jacqueline Landman Gay ___ 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
Re: Port designation in URL
It’s a pipe?? OIC. In that case I am going to say someone meant to type a backslash and had the shift key down instead. Bob S On Dec 12, 2014, at 21:00 , J. Landman Gay jac...@hyperactivesw.commailto:jac...@hyperactivesw.com wrote: It's coming back in the error response from a POST request and the request times out. What does the second port number mean, if that's what it is? ___ 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
Re: Port designation in URL
I think Mike nailed it. The error is being reported by libURL in this case, and the numbers following the pipe are the name it assigns to the socket so it can keep track of the responses. On December 15, 2014 9:45:51 AM CST, Bob Sneidar bobsnei...@iotecdigital.com wrote: It’s a pipe?? OIC. In that case I am going to say someone meant to type a backslash and had the shift key down instead. Bob S On Dec 12, 2014, at 21:00 , J. Landman Gay jac...@hyperactivesw.commailto:jac...@hyperactivesw.com wrote: It's coming back in the error response from a POST request and the request times out. What does the second port number mean, if that's what it is? ___ 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 -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: Port designation in URL
I learn something new everyday. I’ll probably need that bit of information at some point. Hopefully my memory won’t fail me. Bob S On Dec 15, 2014, at 08:16 , J. Landman Gay jac...@hyperactivesw.com wrote: I think Mike nailed it. The error is being reported by libURL in this case, and the numbers following the pipe are the name it assigns to the socket so it can keep track of the responses. On December 15, 2014 9:45:51 AM CST, Bob Sneidar bobsnei...@iotecdigital.com wrote: It’s a pipe?? OIC. In that case I am going to say someone meant to type a backslash and had the shift key down instead. Bob S On Dec 12, 2014, at 21:00 , J. Landman Gay jac...@hyperactivesw.commailto:jac...@hyperactivesw.com wrote: It's coming back in the error response from a POST request and the request times out. What does the second port number mean, if that's what it is? ___ 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 -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: Port designation in URL
Thanks Mike, that helps. Since the error is being processed through libURL it makes sense. On December 13, 2014 1:41:19 AM CST, Mike Bonner bonnm...@gmail.com wrote: If it works like it does in LC, its just assigning a name to the socket, the name being 6928. Its used (again, assuming its used as in lc) so that you can have multiple connects to the same socket on the same host and port so they can be distinguished from one another. Works great when using chatrev (tweaked) for experimenting on a single machine. That way I can talk to myself from multiple stacks at the same time. On Fri, Dec 12, 2014 at 10:00 PM, J. Landman Gay jac...@hyperactivesw.com wrote: A little off topic, but does anyone know what the pipe means in a url in this format: www. domain.com:443|6928 It's coming back in the error response from a POST request and the request times out. What does the second port number mean, if that's what it is? -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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 -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: Port designation in URL
If it works like it does in LC, its just assigning a name to the socket, the name being 6928. Its used (again, assuming its used as in lc) so that you can have multiple connects to the same socket on the same host and port so they can be distinguished from one another. Works great when using chatrev (tweaked) for experimenting on a single machine. That way I can talk to myself from multiple stacks at the same time. On Fri, Dec 12, 2014 at 10:00 PM, J. Landman Gay jac...@hyperactivesw.com wrote: A little off topic, but does anyone know what the pipe means in a url in this format: www. domain.com:443|6928 It's coming back in the error response from a POST request and the request times out. What does the second port number mean, if that's what it is? -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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
