* Yutaka OIWA wrote:
>2) Will the string "http://www.example.com:08080/"; be a valid output of the
> algorithm in Sections 6.1 and 6.2 for some input URIs?
It seems clear to me that "Append a U+003A COLON code point (":") and
the given port, in base ten, to result." does not suggest to prepend
an implementation-defined number of leading zeros. So, no.
>Background:
>I'm writing a draft in HTTPAUTH WG, and considering definition of the canonical
>string for scheme-host-port triple to be chabged in harmony with RFC 6454.
>I need a function which translates "http://www.example.com:08080/";
>into "http://www.example.com:8080";.
Per http://www.ietf.org/mail-archive/web/websec/current/msg01512.html I
would regard RFC 6454 as unsuitable for normative reference, but if you
limit yourself to 'http' and 'https' things might not be that bad.
--
Björn Höhrmann · mailto:[email protected] · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
_______________________________________________
websec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/websec
