On May 5, 8:45 pm, Stephen <sdea...@gmail.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 search
> server is wrong, because it does not refuse to accept raw pipe
> characters.
>
> Certainly, one set of Google servers are wrong, because there are two
> different behaviours.
Accepting a badly-formed URL and doing what the user expects is not
wrong. Not accepting a badly-formed URL is also not wrong. Sending a
badly-formed URL and expecting consistent behavior is, however, wrong.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
