Edit report at https://bugs.php.net/bug.php?id=61439&edit=1
ID: 61439 Comment by: martin dot koranda at gmail dot com Reported by: martin dot koranda at gmail dot com Summary: POST and other methods input data handling Status: Open Type: Feature/Change Request Package: *General Issues Operating System: * PHP Version: 5.4.0 Block user comment: N Private report: N New Comment: mike: yes that's better, parse it regarding on the request content type. it should be also good if it could automatically parse json or xml input, but main is the multipart. do you think you can push your proposal to some of the next builds? Previous Comments: ------------------------------------------------------------------------ [2012-03-20 09:01:37] m...@php.net I second that. Actually I've sitting an unfinished proposal in my Inbox' Drafts which addresses this issue. BUT, I'm not thinking about php.ini, but SAPI code shouldn't care about the request method, but the request body's content type. And there should be an API to register content-type handlers. ------------------------------------------------------------------------ [2012-03-19 17:36:38] martin dot koranda at gmail dot com Description: ------------ when sending multipart/form-data via a POST method, PHP internally parses all variables into $_POST and files into $_FILES. but the parsing is not done with any other method (PUT,PATCH,PROPFIND ..) additionally, sending POST with multipart/form-data makes php://input unavailable. so there is no universal parsing solution which covers all methods. there should be a setting option (php.ini) where i can determine which particular methods i want the internal parser run for (eg. "parse_input_methods = POST,PUT,PATCH") and/or there should be an option for disabling that internal parser completely. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=61439&edit=1
