[ogsa-hpcp-wg] Globus Status

[Peter G. Lane]

Peter G. Lane wrote:
> I figured out what's going on. The .Net implementations at least are 
> using port 443. Globus defaults to 8443. Could everyone perhaps make a 
> point of including explicit port numbers in they're service URLs? The 
> problem as I understand it is this: *Nix machines have a port 
> restriction on low ports, which makes it impossible to start a web 
> service container on 443 without it being run as root. Windows has no 
> such restriction. So while 443 is technically the standard for https, 
> non-.Net web service containers conventionally use 8080 for http and 
> 8443 for https transport so that non-root users can stand up containers.

I seem to be the only one assuming 8443 instead of 443, so don't worry about my request for explicit 
port numbers.

> 
> Peter
> 
> Glenn Wasson wrote:
>> When I said "HTTP GET", I didn't mean to imply "it's not using HTTPS". 
>> IIS's
>> logs show that it's getting a connection on port 443, so I'm guessing 
>> that
>> the HTTPS part is working. I was actually referring to using GET 
>> instead of
>> POST and I wasn't sure if your client initially does a GET to check 
>> the WSDL
>> (or something).
>>
>> Glenn
>>
> 
> 
> ------------------------------------------------------------------------
> 
> --
>   ogsa-hpcp-wg mailing list
>   ogsa-hpcp-wg at ogf.org
>   http://www.ogf.org/mailman/listinfo/ogsa-hpcp-wg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3804 bytes
Desc: S/MIME Cryptographic Signature
Url : http://www.ogf.org/pipermail/ogsa-hpcp-wg/attachments/20061106/0abdfd04/attachment-0001.bin