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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
