[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-06 Thread Tag++
To Wooble, I can't separate bad from error,fault or wrong results, as a normal/ general/ordinary user I just click on this link to open it http://admins.googleapps.com/system/app/pages/search?q=error|400 I got a correct/exact/right results and then I focus on browser's address box and press

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Tag++
You are right. /search?q=a|b work fine on google others search engine too, I think the problem placed in ghs.google.com On May 5, 3:15 am, Wooble geoffsp...@gmail.com wrote: RFC1738 requires unsafe characters, including '|', to be urlencoded. Why this works on appspot is a mystery, but I'd

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Nick Johnson (Google)
Hi, '|' characters in URLs should be escaped as %7C. Web browsers will do this for you, but if you're constructing URLs yourself, it's up to you to escape them properly. -Nick Johnson --~--~-~--~~~---~--~~ You received this message because you are subscribed to

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Tag++
barryhunter, I see what Wooble said. I am a visitor of http://admins.googleapps.com/ I open this site with Firefox browser and input error|400 into the search box which located in top right of screen, and press the Search Site button to submit this query, and I got a response of: Your search

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Tag++
Nick Johnson, IE can convert '|' to %7C but Firefox will not! I (a normal visitor) didn't constructing any URL, so this is not Vistor's or Firefox's business, this is Web Server's matter I know some kind of Web Server can handle '|' char, including App Engine, and I am sure something failed on

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Nick Johnson (Google)
Firefox will send your URL exactly as you enter it, yes. But if you fill out a form (such as a search box) in Firefox, it will correctly URL-escape the | character for the URL. Internet Explorer behaves in the same manner, so any URL generated by a form will have the | character correctly

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Tag++
To Nick Johnson, But if you fill out a form (such as a search box) in Firefox, it will correctly URL-escape the | character for the URL Is this real? but my Firefox 3.0.4(Windows XP) or Chrome 1.0.154.59 (Windows XP) always keep the '|' in the address box!!! I have try this test on google

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Nick Johnson (Google)
On Tue, May 5, 2009 at 11:28 AM, Tag++ tagpp.ad...@gmail.com wrote: To Nick Johnson, But if you fill out a form (such as a search box) in Firefox, it will correctly URL-escape the | character for the URL Is this real? but my Firefox 3.0.4(Windows XP) or Chrome 1.0.154.59 (Windows XP)

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Tag++
To Nick Johnson, http://www.google.com/search?hl=enq=error|400+^bad+~request+{goog}+\to+[OR]+`go`btnG=Search http://search.yahoo.com/search?hl=enq=error|400+^bad+~request+{goog}+\to+[OR]+`go`btnG=Search http://en.wikipedia.org/wiki/Special:Search?search=error|400+^bad+~request+{goog}+\to+[OR]

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Nick Johnson (Google)
The RFC is clear as to what characters are acceptable in the query string part of a HTTP URL. | is not one of these characters, so if your browser is sending one, it's an issue either with your browser or with your URL encoding. -Nick Johnson

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Tag++
To Nick Johnson, I am normal visitor now, I didn't do any URL encoding, I use the popular browser, including Chrome from google. I want to making a comparison between popular Web Server(Google Search Server,Yahoo Search Server,Wikipedia.org) and RFC follower (ghs.google.com:

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Stephen
On May 5, 11:13 am, Nick Johnson (Google) nick.john...@google.com wrote: Google's servers returning a 400 for URLs containing an unescaped | character is not a bug in the server - they're correctly obeying the relevant RFCs. By this definition, you are claiming that the main google.com

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-05 Thread Tag++
Like others general visitors, I often copy a url from address box and share to friends If you submit a search by click 'Search' button, Firefox will escape '|' to '%7c' and send to Web Server, but it will keep '|' remain in the address box If you paste 'error%7C400' to Firefox and press enter

[google-appengine] Re: Error 400: app engine + custom domain + /search?q=a|b|c

2009-05-04 Thread Wooble
RFC1738 requires unsafe characters, including '|', to be urlencoded. Why this works on appspot is a mystery, but I'd guess having it fail on a google apps domain has something to do with how ghs handles mapping URLs to applications. On May 3, 4:30 am, Tag++ tagpp.ad...@gmail.com wrote: Hi,all