On Sep 1, 6:41 pm, jmathai <[email protected]> wrote:
> That's a valid point.  What do you think of following on GETs and
> throwing an exception for POSTs?  Not sure many people like to deal
> with exceptions (I prefer them).

It would be helpful if someone from Twitter or who has done some
extensive testing of the 302 behavior could chime in.

IF re-trying the request after NOT following a 302 on a POST doesn't
bypass the DDoS countermeasure than throwing an exception is
completely useless.  IF re-trying the request after encountering a 302
DOES work, than throwing an exception would be sufficient to solve the
problem.

Personally I'd rather just see the library follow the 301/302 on POST
and GET, but I can see where throwing an exception would be the more
"compliant" approach.

Can someone chime in on this please?

Reply via email to