"Be liberal in what you accept, and conservative in what you send." may be Jon Postel's most famous quote, but it is not his best contribution to the internet.
It seemed like a good idea at the time, when the number of senders and the complexity were both low. Experience has taught us that being tolerant on the receiving end has two really bad consequences: 1) What YOU think the sender meant, may not be what the sender actually meant. 2) It encourages a proliferation of broken senders. Case in point for both: HTML That's why so many subsequent RFCs go to pains to explicitly REQUIRE that non-conforming inputs be rejected. Anyway, conforming parsers have ALWAYS thrown exceptions when given a space. Some browsers, however, will convert spaces for you if you enter them into your browser address bar. A few will even tolerate them in HTML pages, as a sop to people with broken HTML pages. Of which there are an incredible number. It's always a bad idea to try to infer standard behavior from observed behavior. It's an especially bad idea to do so when a browser is involved! Fortunately, it's easy to Google up a standard these days and check. Note that historically, prior to RFC 2396, the standard for URL's was somewhat looser than for URIs. But it was never loose enough to accept spaces. On Mar 29, 11:58 am, Michael Thomas <[email protected]> wrote: > Though you can say that both violate RFC1122 :) > > Mike, section 1.2.2, though a fair number of people in the internet > community think > that was wrong > > > > Mark Murphy wrote: > > DonFrench wrote: > > >> It is perfectly legal for a URL to contain an embedded space in > >> certain situations, such as in this example: > >>http://maps.google.com/maps?q=37.265632,+-122.2468(10:33 > >> PM)&iwloc=A&hl=en. > > > The IETF would disagree with your assertion: > > >http://tools.ietf.org/html/rfc3986 > > > Note that the space is not in the reserved character set (section 2.2) > > or the unreserved character set (section 2.3), and so therefore is not > > legal in a URL without being encoded. > > > For a more readable summary: > > >http://en.wikipedia.org/wiki/URL_encoding > > > If you have another authority that says spaces are legal in URLs, point > > it out! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
