On Tue, 12 Nov 2002, Hartmut Holzgraefe wrote: > the current problem with HTTP_RAW_POST_DATA is just that > i never really figured out when it should be populated > depending on HTTP method, Content type and > always_populate_raw_post_data, this is going to be fixed > today
Okay. > besides the HTTP_RAW_POST_DATA issue what i did was > a cleanup of the HTTP content handler code in SAPI.c > that fixes problems with PHP not comsuming content > data although at least the apache 1.x API relies on > it (for keepalive connections) That needs to be tested pretty well, I imagine? > php://input works for the apache sapi, but not with CGI > i had no time yet to realy dig into it but i'm pretty sure > it is a problem within the CGI sapi code and not in the > content handler ... > > i definetly want this feature in 4.3 as with plain 4.2.x > it is impossible to handle PUT and WebDAV requests and even > with the allow_webdav_methods patch and HTTP_RAW_POST_DATA > extended to PUT and WebDAV specific methods you get back > the same memory consumption problems as with file uploads > before 4.2.0 This php://input thing is what concerns me. How much time do you need to finish and test it? We don't want to delay RC1 too much. -Andrei http://www.gravitonic.com/ "Someone clearly thinks that C is a garbage collected language" -- Morten Welinder -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
