* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #66 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Allow %-encoding to punycode conversion for ireg-name?

Reported by: duerst@it.aoyama.ac.jp Owned by:
Priority: major Milestone:
Component: 3987bis Version:
Severity: - Keywords:
Cc:

Description

Taken out of draft -04:
DESIGN QUESTION: What about e.g. http://r%C3%A9sum%C3%A9.example.org in an IRI? Will that get converted to punycode, or not?

Change History

comment:1 Changed 3 years ago by masinter@adobe.com

Section 3.4.2. Mapping using Punycode

should first require that sequences of %xx hex-encoded octets be translated back to unicode if they are valid UTF-8 sequences, and that sequences that are not valid UTF-8 are not allowed, should be left alone (since there is no valid conversion to punycode.)

comment:2 Changed 3 years ago by masinter@adobe.com

  • Status changed from new to closed
  • Resolution set to fixed

Resolution: inserted at top of section 3.4.2 Mapping using Punycode:

If there are any sequences of <pct-encoded>, and their
corresponding octets all represent valid UTF-8
octet sequences, then convert these back to Unicode
character sequences. (If any <pct-encoded> sequences are not
valid UTF-8 octet sequences, then leave the entire field as is
without any change, since punycode encoding would not succeed.)

Note: See TracTickets for help on using tickets.