Changeset 13


Ignore:
Timestamp:
Sep 21, 2010, 12:58:55 AM (9 years ago)
Author:
duerst@…
Message:

removed an open issue in the draft because it was moved to the tracker as http://trac.tools.ietf.org/wg/iri/trac/ticket/40.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-iri-3987bis/draft-ietf-iri-3987bis.xml

    r12 r13  
    23442344<t hangText="dealing with disallowed IRI characters"> </t>
    23452345
    2346 <t hangText="Special Query Handling needed?">
    2347 The percent-encoding handling of query components in the HTTP scheme
    2348 is really unfortunate. There is no good normative advice to give if
    2349 the percent-encoding is delayed until the query-IRI is interpreted. Could
    2350 HTML ask browsers to percent-encode the form data using the document
    2351 character set BEFORE the query IRI is constructed, and only in the case where
    2352 the document character set isn't Unicode-based and the query is
    2353 being added to http: or https: URIs?  This would give more
    2354 consistent results.  Browsers might have to change their behavior in
    2355 constructing the IRI-with-query-added, but the results would be more
    2356 consistent and fewer bugs, and it wouldn't affect interpretation of
    2357 any existing web pages. It would remove the need to have a normative
    2358 special case for queries in HTML documents, just for http, in a way
    2359 in which things like transcoding etc. wouldn't work well.  You could
    2360 tell the difference between a query URI in the address bar and one
    2361 created via a form because the address bar would always be UTF-8.
    2362 The browsers might have to change the algorithm for showing the address
    2363 in the adress bar to know how to undo the encoding.</t>
    2364 
    23652346<t hangText="handling illegal characters">
    23662347
Note: See TracChangeset for help on using the changeset viewer.