[Webkit-unassigned] [Bug 54271] safari-extension: scheme needs special case-sensitive treatment in KURL

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=54271


Timothy Hatcher <timothy at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #82121|review?, commit-queue?      |review-
               Flag|                            |




--- Comment #5 from Timothy Hatcher <timothy at apple.com>  2011-02-11 08:02:55 PST ---
(From update of attachment 82121)
View in context: https://bugs.webkit.org/attachment.cgi?id=82121&action=review

> Source/WebCore/platform/KURL.cpp:1354
> +            // safari-extension: host contents are case sensitive (in violation of RFC 2396).
> +            // https://bugs.webkit.org/show_bug.cgi?id=54271

No where in RFC 2396 do I see that safari-extension is in violation.

> This authority component is typically defined by an Internet-based
> server or a scheme-specific registry of naming authorities.

And:

> The structure of a registry-based naming authority is specific to the
> URI scheme, but constrained to the allowed characters for an
> authority component.
>
>     reg_name      = 1*( unreserved | escaped | "$" | "," |
>                          ";" | ":" | "@" | "&" | "=" | "+" )

And "unreserved" is defined as (expanded) "lowalpha | upalpha | digit | mark".

Only if the scheme uses "Server-based Naming Authority" does the case-insensitive domain name logic apply.

> Hostnames take the form described in Section 3 of [RFC1034] and section 2.1 of [RFC1123]

So I disagree that "safari-extension" is in violation, and that any domain canonicalization should only apply to schemes we know treat the athority as server-based. I would also argue that this should apply to security origin too. Only the scheme is called out as being case-insensitive for all URIs.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.