You want RFC 1738 (Uniform Resource Locators): http://www.faqs.org/rfcs/rfc1738.html and section 3.2 of RFC 2616 (HTTP): http://www.faqs.org/rfcs/rfc2616.html
Neither spec actually requires that the query string take a particular form, other than specifying what characters are valid in that part of the URL. The standard key/value format you usually see used is the "application/x-www-form-urlencoded" mime type, defined in the HTML specification (http://www.w3.org/TR/html401/interact/forms.html#form-content-type). There's no obligation to adhere to that standard when generating your own URLs, though - it merely specifies what HTML forms can generate. -Nick Johnson On Thu, May 14, 2009 at 10:46 PM, codingGirl <[email protected]> wrote: > > I already happy if I do not violate any URL syntax specifications by > just writing &ishere > > Where can I find the specification that says I do it correctly? > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
