Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:40806 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66038 invoked from network); 30 Sep 2008 07:42:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Sep 2008 07:42:43 -0000 Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; 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:20833] helo=il-gw1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 10/11-36431-278D1E84 for ; Tue, 30 Sep 2008 03:42:43 -0400 Received: from ws.home ([10.1.1.1]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 30 Sep 2008 10:42:49 +0300 Message-ID: <48E1D86E.40704@zend.com> Date: Tue, 30 Sep 2008 11:42:38 +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> <48E0F994.8010802@zend.com> <48E1C3DF.5040604@lerdorf.com> In-Reply-To: <48E1C3DF.5040604@lerdorf.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Sep 2008 07:42:49.0418 (UTC) FILETIME=[23196AA0:01C922D0] Subject: Re: [PHP-DEV] ext/soap and http header From: dmitry@zend.com (Dmitry Stogov) Rasmus Lerdorf wrote: > Dmitry Stogov wrote: >> 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. > > Well, for one a bunch of the internal Yahoo web services require a > certificate header. I doubt we are the only Web company who needs to > authenticate the higher-level users of lower-level web services. > > We are running with Brian's patch now, but I don't really see the reason > not to make it possible for people to set custom headers on web services > requests. I see. It's not a problem. I'll look and probably add the patch on this week. Thanks. Dmitry. > Another example is the Weather Underground API. They ask you to set the > User-Agent to your email address so they can contact you if your app > starts causing them problems. > > -Rasmus