Turns out after all that - it was my system clock being wrong. Our dev server clock keeps screwing up. The 401 wasn't descriptive enough for me to diagnose this. It was actually Amazon S3's descriptive error that let me to this solution
- [twitter-dev] Sudden OAuth failures from a specific IP address timwhitlock
- [twitter-dev] Re: Sudden OAuth failures from a specific I... timwhitlock
- Re: [twitter-dev] Sudden OAuth failures from a specific I... Ryan Sarver
- [twitter-dev] Re: Sudden OAuth failures from a specif... timwhitlock
- [twitter-dev] Re: Sudden OAuth failures from a sp... timwhitlock
- [twitter-dev] Re: Sudden OAuth failures from ... timwhitlock
