Re:Apple's HTTP POST caching is a bug
by damncabbage on Sunday September 23, 2012 @06:10PM
(#4562258)
PUTs of URI-encoded XML queries in the request URL, ...
Or POST-only AJAX requests because an out-of-the-box install of a package wants to put 5KB of data into the URL: http://drupal.org/node/956186
Re:Apple's HTTP POST caching is a bug
by lollerpops on Sunday September 23, 2012 @10:30PM
(#4562934)
So what's the fix? I want to GET something that has an 8k long name. What do I do?
Re:Apple's HTTP POST caching is a bug
by damncabbage on Sunday September 23, 2012 @11:20PM
(#4563052)
I have an 8-foot toenail that needs a little clipping; what tool should I use?
More seriously, what needs an 8KB-long name?
(That bug post contains a few workarounds that'll let Drupal get back to GET for one of the listed cases. Drupal's case is particularly pathological as it's trying to be everything to everybody; it's like being a handsaw AND a sander AND a varnish for the floor AND a dessert topping.)
Re:Apple's HTTP POST caching is a bug
by lollerpops on Monday September 24, 2012 @10:44PM
(#4568265)
A file storage service, ala dropbox, that allows you to select multiple files and download them as a zip. The concatenation of several uuids adds up quickly.
Re:Apple's HTTP POST caching is a bug
by damncabbage on Tuesday September 25, 2012 @07:58AM
(#4569849)
Good point. Unbounded requests (hundreds or more of ten-char IDs) are definitely candidates for a POST workaround. It's a shame, but necessary. :S
My main beef with Drupal is that it uses POST for everything, whether it's to /jobs/1234 or to /files/?id[]=1234&id[]=3452&...
Use POST. GET is not meant for that amount of data. Alternatively, GET by a shorter ID.
Re:Apple's HTTP POST caching is a bug
by lollerpops on Sunday September 23, 2012 @10:43PM
(#4562961)
What do I do about the people who tell me POST is only for actions which change server state?
You write a well documented application that is useful, adheres to as much of REST as you can and leave the theories to other people.
Re:Apple's HTTP POST caching is a bug
by drivebyacct2 on Monday September 24, 2012 @01:18AM
(#4563321)
Simultaneously, it seems to indeed be a convention. And why not follow it? Do you have something whose keys really require the numerousness of 8KB of characters?
Not to get all Bladerunner here, but I've seen things you people wouldn't believe. PUTs of URI-encoded XML queries in the request URL, right up until the HTTP server says "Nope, 8K is your limit" for a start...