> > I can live with either solution here, but GET requests are the wrong > thing to use here per the HTTP spec. Per HTTP GET requests are not > supposed to have side effects, and we definitely expect server to have > side effects like logging the beacon. > Also, GET requests aren't supposed to have a request body IIRC. Point taken around side-effects, but there are specs, and then there is how these tools get used in the real world.. As long as I can make a simple GET without payload, I'm good. :) On Thu, Nov 7, 2013 at 11:33 AM, Jonas Sicking <jonas@sicking.cc> wrote: > Actually, if we want to add a timeout argument in the future (after > which the beacon is dropped on the floor) that would also be a reason > to make the last argument a dictionary for now. > +1
Received on Thursday, 7 November 2013 19:49:39 UTC