Path: csiph.com!usenet.pasdenom.info!goblin2!goblin.stu.neva.ru!news.internetdienste.de!noris.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="ISO-8859-1" Message-ID: <6503747.LP8xm1ciM4@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Sun, 26 Aug 2012 21:43:58 +0200 User-Agent: KNode/4.4.11 Content-Transfer-Encoding: 7Bit X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&. <4919648.gLsDIqzOUs@PointedEars.de> <2094311.UPhlsrQmMF@PointedEars.de> <7781613.3ztUY42lFh@PointedEars.de> Followup-To: comp.lang.php MIME-Version: 1.0 Lines: 28 NNTP-Posting-Date: 26 Aug 2012 21:43:58 CEST NNTP-Posting-Host: 2fb67476.newsspool3.arcor-online.net X-Trace: DXC=Y1JPOlNL8FR[7Non7UCi8UMcF=Q^Z^V3X4Fo<]lROoRQ8kF On 2012-08-26 19:15, Thomas 'PointedEars' Lahn wrote: >> Christoph Becker wrote: >>> So for POST requests, when the Content-Type is text/plain (e.g. by using >>>
) even non-ASCII characters in the body can >>> be sent directly. But not all server side "languages" will handle this >>> (e.g. PHP will not fill in the $_POST variable). >> PHP is not supposed to fill the $_POST array then; there are no >> parameters. Indeed, apparently there is no trivial way, if any, to >> retrieve the message body with PHP then [...] > > file_get_contents("php://input") Thanks, unfortunately it requires allow_url_fopen=1. > or any other function capable of reading from streams. Could you provide an example, please? F'up2 comp.lang.php PointedEars -- Danny Goodman's books are out of date and teach practices that are positively harmful for cross-browser scripting. -- Richard Cornford, cljs, (2004)