Port designation in URL

[J. Landman Gay]

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 <bonnmike at 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
><jacque at 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         |     jacque at hyperactivesw.com
>> HyperActive Software           |     http://www.hyperactivesw.com
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at 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 at 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         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com