3 ms·

Why not POST requests for anything that changed server-side state?

• ars 12y ago
  Obviously that is the solution. I know that now, I didn't then. (As I wrote: "I did eventually fix it by switching to forms.") The whole thing about POST vs GET that everyone knows today for read only vs write was not that well known back then. Back then you used GET for things with a small number of variables, and POST when you expected enough data that it wouldn't fit in the URL. It was all about the URL, not about the effect of the request.
  • shiggerino 12y ago
    Ah, I see. Should have picked that up. I guess there was no Wikipedia to have an article for HTTP back then, which has been an invaluable resource for me to understand some of the intricacies in my work.
  • girishso 12y ago
    I remember those days. Those days only two methods existed, GET and POST! ;)
  • freedombeer 12y ago
    Re: GET and POST differences and usage has always been pretty clear if you read the RFCs. RTFM.