[twitter-dev] Re: 413 Request Entity Too Large for Direct Message

2010-07-02 Thread El Greg
Thanks, Taylor. Turns out I was being a bit of an idiot and not including the POST parameters correctly in my curl request. Apparently the error when you POST to a signed URL without any POST data is this 413 business. Thanks again for the reply, Greg On Jun 16, 4:49 pm, Taylor Singletary wr

Re: [twitter-dev] Re: 413 Request Entity Too Large for Direct Message

2010-06-16 Thread Taylor Singletary
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

[twitter-dev] Re: 413 Request Entity Too Large for Direct Message

2010-06-16 Thread El Greg
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 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 > f