On Mon, Sep 19, 2011, Tim Hoffman <[email protected]> wrote: > I think google are saying they are reserved as guide so you don't clash with > some service of theirs, however I don't actually see > any way of preventing you from using any of these paths in urls if you > handling them yourself. > In my case I don't use webapp and don't only map a few of the _ah paths, and > so my default handler gets all forms of /form as well as /_ah/* that don't > match existing mapped handlers in app.yaml. > The danger is you prevent the access of some useful appengine service.
Tim, Thanks for your reponse. Yes, for some /_ah/ paths, you're even supposed to handle them yourself. For example, the Python warmup handler. But I couldn't get my code to handle /form (not /form/ or /form/something, but /form itself). Google's built-in handler always takes precedence and returns a Google-branded 404 page with a nice robot image. So the issue with /form is not theoretical. What do you use /form for? Regards, Alexander -- 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.
