$_POST is useful for FORM data -- it urldecodes the data, and assumes it's something somebody would actually type into a FORM. This would be what 99.9% of websites need and want. $HTTP_RAW_POST_DATA gives you ALL the raw encoded data to parse as you see fit. This covers the rest of the needs. If you need something even more arcane than either of those, run your own service on your own socket. On Sat, September 23, 2006 3:35 am, Marek 'MMx' Ludha wrote: > Accessing $HTTP_RAW_POST_DATA is similar to reading php://input which > I mentioned in my previous email. > I am not quite sure what is $_POST useful for. It is intended for > reading urlencoded data which it does only in special cases (no \0 or > \5C chars) and everyone has to parse it himself. Did I miss something? > > -- > Marek 'MMx' Ludha > > On 9/23/06, Richard Lynch <ceo@xxxxxxxxx> wrote: >> >> >> Search php.net for RAW_HTTP_POST or somesuch. >> >> It's there for ya. >> >> >> >> -- >> Like Music? >> http://l-i-e.com/artists.htm >> >> >> > -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
