-----Original Message-----
From: oauth@googlegroups.com [mailto:oauth@googlegroups.com] On Behalf Of Dirk Balfanz
Sent: Friday, March 28, 2008 2:38 PM
To: oauth@googlegroups.com
Subject: [oauth] url construction for signature base string underspecified?

Hi guys,

so I'm trying to figure out how to normalize the URL part of the
signature base string. The spec (section 9.1.2), strangely, says that
the port MUST be included, but the "http default port 80 and https
default port 443 MUST be excluded". There is also an example:

HTTP://Example.com:80 maps to http://example.com
Presumably, something like http://example.com:1234 would map to
http://example.com:1234

Here is my question: what should https://example.com:80 and
http://example.com:443 map to? In other words, is the language in
Section 9.1.2 supposed to mean that the port is to be removed if it
happens to be the standard port for the protocol specified? Or are
ports 80 and 443 to be removed no matter what?

Confused,

Dirk.

On Fri, Mar 28, 2008 at 11:44 AM, Eran Hammer-Lahav <e...@hueniverse.com> wrote:

>  https://example.com:80 and http://example.com:443 stay just like that. You only drop 80 for http and 443 for https.

>  EHL

>  -----Original Message-----
>  From: oauth@googlegroups.com [mailto:oauth@googlegroups.com] On Behalf Of Dirk Balfanz
>  Sent: Friday, March 28, 2008 2:38 PM
>  To: oauth@googlegroups.com
>  Subject: [oauth] url construction for signature base string underspecified?

>  Hi guys,

>  so I'm trying to figure out how to normalize the URL part of the
>  signature base string. The spec (section 9.1.2), strangely, says that
>  the port MUST be included, but the "http default port 80 and https
>  default port 443 MUST be excluded". There is also an example:

>  HTTP://Example.com:80 maps to http://example.com
>  Presumably, something like http://example.com:1234 would map to
>  http://example.com:1234

>  Here is my question: what should https://example.com:80 and
>  http://example.com:443 map to? In other words, is the language in
>  Section 9.1.2 supposed to mean that the port is to be removed if it
>  happens to be the standard port for the protocol specified? Or are
>  ports 80 and 443 to be removed no matter what?

>  Confused,

>  Dirk.