- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 25 Oct 2011 11:13:58 +1100
- To: public-iri@w3.org
- Cc: Chris Weber <chris@lookout.net>, Larry Masinter <masinter@adobe.com>
I think we've already looked at this (would have to dig around), but it's not out of scope, it'd be WONTFIX -- interoperable behaviour is already clearly defined, and we can't make most of the servers on the planet non-conformant just because a few clients get it wrong. Cheers, On 22/10/2011, at 10:17 AM, iri issue tracker wrote: > #36: Some HTTP implementations send UTF8 path directly > > Changes (by masinter@…): > > * status: new => closed > * resolution: => wontfix > * component: 3987bis => 4395bis > > > Comment: > > I don't see what change to 3987bis would be helpful. > I might see 4395bis urging updates to existing IRI specs? > > Would the HTTP working group will declare this out of scope? > > -- > ----------------------+---------------------- > Reporter: duerst@… | Owner: > Type: defect | Status: closed > Priority: major | Milestone: > Component: 4395bis | Version: > Severity: - | Resolution: wontfix > Keywords: | > ----------------------+---------------------- > > Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/36#comment:3> > iri <http://tools.ietf.org/wg/iri/> > > -- Mark Nottingham http://www.mnot.net/
Received on Tuesday, 25 October 2011 00:14:37 UTC