I based my statement on the fact that the example I gave works correctly (treating the space as just another character) in all the browsers I tested it on, which wasn't that many (IE 8 and FF3.6.2). I assumed that if it worked it was valid, which obviously isn't necessarily true.
On Mar 29, 11:52 am, Mark Murphy <[email protected]> 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! > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Warescription: Three Android Books, Plus Updates, One Low Price! -- 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.
