Hi Greg,

Do you have any kind of HTTP proxy active in your other location? It's
definitely possible that they are messing with HTTP headers or proxying the
request in some way.

Though unrelated, you'll want to make sure that the time on your server is
within a reasonable amount of drift from our server time (which is included
in a HTTP header of every request).

Is just this particular POST request failing in your site5 server, or all
POST requests?

Taylor Singletary
Developer Advocate, Twitter

On Wed, Jun 16, 2010 at 1:08 PM, El Greg <greglaval...@gmail.com> wrote:

> Bump - any idea on this? I'm trying to switch my app to OAuth before
> the big switch at the end of June.
> Thanks,
> Greg
> On Jun 13, 10:32 pm, El Greg <greglaval...@gmail.com> wrote:
> > Hi there - I'm trying to get set up with the new OAuth API for a
> > little app that I'm hosting on site5. When make a signed POST request
> > from the app on my home machine, it works just fine. When I have the
> > application do it on my host, the response to my curl request is a 413
> > Requet Entity Too large and looks like this (hope it comes out):
> >
> > <html><head>
> > <title>413 Request Entity Too Large</title>
> > </head><body>
> > <h1>Request Entity Too Large</h1>
> > The requested resource<br />/direct_messages/new.json<br />
> > does not allow request data with POST requests, or the amount of data
> > provided in
> > the request exceeds the capacity limit.
> > <p>Additionally, a 413 Request Entity Too Large
> > error was encountered while trying to use an ErrorDocument to handle
> > the request.</p>
> > </body></html>
> >
> > I'm not sure if I want to post the entire signed request and its
> > parameters for security reasons.  I can't understand why it would work
> > locally and not up on the server... Is it possible that my web host is
> > attaching some junk to the request that twitter is rejecting?

Reply via email to