I'll file a bug for it. I hit into a similar issue as well:
HTTP DELETE requests can have a body defined when calling the dev server, but when calling the live server you get a 400 bad request with zero info on the admin logs that the request even occurred - it does not show in errors or anywhere else! This is actually an existing issue from 2008 (!!!) http://code.google.com/p/googleappengine/issues/detail?id=601 If the dev server sdk could be updated to match this behavior at least it would be a pretty big improvement considering RestyGWT and similar clients do send a method body by default if you use the standard @Attribute methods. On Fri, Jan 4, 2013 at 8:00 PM, ludovic Champenois <[email protected]> wrote: > On 1/4/13 7:51 AM, Ryan Chazen wrote: > >> Is there any way to run unit tests on appengine directly instead of >> running them only on the dev server? >> >> At any rate, the error is not from the multiple query parameters, but >> rather (found from a Google search), that the addHeader method on AppEngine >> live does not accept nulls while the dev server does. >> >> The javadocs don't specify if it can or can't accept nulls, so I'm not >> sure what the correct behavior is. >> http://docs.oracle.com/javaee/**5/api/javax/servlet/http/** >> HttpServletResponse.html#**addHeader%28java.lang.String,%** >> 20java.lang.String%29<http://docs.oracle.com/javaee/5/api/javax/servlet/http/HttpServletResponse.html#addHeader%28java.lang.String,%20java.lang.String%29> >> >> However, the live and dev server really should both function the same way >> - either the dev server should disallow nulls or the live should allow them. >> It makes testing difficult if live and dev server behave differently. >> > > I agree. Please file a bug and will take care of it. My preference is to > fix it at the SDK level. > > Ludo > > >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To view this discussion on the web visit https://groups.google.com/d/** >> msg/google-appengine/-/**1dGUFsY7JDsJ<https://groups.google.com/d/msg/google-appengine/-/1dGUFsY7JDsJ> >> . >> To post to this group, send email to >> google-appengine@googlegroups.**com<[email protected]> >> . >> To unsubscribe from this group, send email to >> google-appengine+unsubscribe@**googlegroups.com<google-appengine%[email protected]> >> . >> For more options, visit this group at http://groups.google.com/** >> group/google-appengine?hl=en<http://groups.google.com/group/google-appengine?hl=en> >> . >> > > -- > 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<[email protected]> > . > To unsubscribe from this group, send email to > google-appengine+unsubscribe@**googlegroups.com<google-appengine%[email protected]> > . > For more options, visit this group at http://groups.google.com/** > group/google-appengine?hl=en<http://groups.google.com/group/google-appengine?hl=en> > . > > -- 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.
