Only the makeRequest handler accepts POST, and it must be sent in the makeRequest format. The 'open' or 'embed' proxy is a bit more liberal in what it allows, but it only handles GET and HEAD requests.
Shindig does not expose a transparent proxy, as that would create major complications for securing the service. On Sat, Apr 11, 2009 at 7:06 AM, Adam Dean <[email protected]> wrote: > We are porting a Google Web Toolkit (version 1.5.3) client/server > application to a Gadget. > The app utilizes the GWT RPC framework to communicate to the server > services. > > I am converting the service calls to utilize the Shindig Proxy, as > described in the Google FAQ and that's where I run into a Shindig > limitation. > > The GWT RPC sends the request as a POST, but I am receiving a 405 Error > (The specified HTTP method is not allowed for the requested resource ().) > It seems the Shindig Proxy is rejecting POST requests. I've started > tracing through the Shindig code, but figured I might get better advice > from this list. > I haven't found how I can configure GWT RPC to use a GET. > > So, is there some way to allow the Proxy to handle POSTs? or is there a > reason for this limitation? or is the a new Bug/Feature request? > > Thanks for any help available, > Adam >
