Re: New Standardized HTTP Interface
| From: | Sanford Whiteman | Date: | Thu, 06 Nov 2014 03:03:33 +0000 |
| Subject: | Re: New Standardized HTTP Interface | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-78776@lists.php.net to get a copy of this message | ||
For the umpteenth time, *in what situation must you PUT multipart/form-data or
multipart/x-www-form-urlencoded only to treat it, semantically, as a POST*? Which UA cannot send a
POST? It's like we're completely upside down on this thread.
If you're PUTing such POSTful content-types for any reason other than storing the entire
resource, you're doing HTTP wrong. Truthfully: if someone said, "Yeah, so we got into
PUT lately, we use it for Ajax form, er, posts, for, um, speed or something," would you not be
like, "Wat?"
-- S.