Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:40780 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44103 invoked from network); 29 Sep 2008 15:51:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Sep 2008 15:51:56 -0000 Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.163 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 212.25.124.163 il-gw1.zend.com Windows 2000 SP4, XP SP1 Received: from [212.25.124.163] ([212.25.124.163:17723] helo=il-gw1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/06-36431-999F0E84 for ; Mon, 29 Sep 2008 11:51:55 -0400 Received: from ws.home ([10.1.1.1]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 29 Sep 2008 18:51:59 +0300 Message-ID: <48E0F994.8010802@zend.com> Date: Mon, 29 Sep 2008 19:51:48 +0400 User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Rasmus Lerdorf CC: "Brian J. France" , internals@lists.php.net References: <1890A80D-FE2B-413C-9B41-C56FB17B865D@firehawksystems.com> <48E08DBC.7060000@zend.com> <48E0E9B0.7010604@lerdorf.com> In-Reply-To: <48E0E9B0.7010604@lerdorf.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Sep 2008 15:51:59.0770 (UTC) FILETIME=[4EDBF7A0:01C9224B] Subject: Re: [PHP-DEV] ext/soap and http header From: dmitry@zend.com (Dmitry Stogov) Hi Rasmus, Rasmus Lerdorf wrote: > Dmitry Stogov wrote: >> Hi Brian, >> >> I think you patch does the things you like properly, but why do we need >> such ability? I don't see a use-case. >> >> In case of accepting this patch, we also need to care about duplicate >> headers. > > Some web services require custom headers for authentication or to bounce > along information about the originating request in order to do proper > logging and accounting about which top-level users are causing the > backend web services requests. Could you give an example. Thanks. Dmitry.