Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95866
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CANUQDChoKhUZsJE6Ja8PNEJd6mrBzMCD2T3JJ+LfoGbF8LvnGQ@mail.gmail.com>
References: <CAA69SC6szFdRLAhmPuWf2VJb2RyWH0L=-DoVFqrOo74qomwSXA@mail.gmail.com>
 <CANUQDChoKhUZsJE6Ja8PNEJd6mrBzMCD2T3JJ+LfoGbF8LvnGQ@mail.gmail.com>
Date: Fri, 9 Sep 2016 16:30:35 +0200
Message-ID: <CAA69SC4TxNkqdJG7882JovaAFsso-782Lfih58MhO=QOmCgy6Q@mail.gmail.com>
To: Niklas Keller <me@kelunik.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e010d871458efe4053c13fd0d
Subject: Re: [PHP-DEV] [PHPDEV] Bearer Auth
From: marijic.silvio@gmail.com (=?UTF-8?Q?Silvio_Mariji=C4=87?=)

--089e010d871458efe4053c13fd0d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

@Niklas
We are already supporting Basic and Digest and Bearer and MAC are used
widely as a form of token authorization.

2016-09-09 14:37 GMT+02:00 Niklas Keller <me@kelunik.com>:

> 2016-09-09 14:17 GMT+02:00 Silvio Mariji=C4=87 <marijic.silvio@gmail.com>=
:
>
>> Came across this issue https://bugs.php.net/bug.php?id=3D72915 and got a=
n
>> idea. I've added PHP_AUTH_BEARER to $_SERVER when Bearer auth token is
>> used
>> as Authorization method.
>>
>> Does this kind of change requires RFC ? Would this kind of change be
>> usefull enough to go into the codebase ?
>>
>> Here are the changes I made:
>> https://github.com/php/php-src/compare/master...smarijic:php_auth_bearer
>>
>> Cheers,
>> Silvio.
>> --
>> Silvio Mariji=C4=87
>> Software Engineer
>> 2e Systems
>>
>
> I don't see why we should special case Bearer tokens.
>
> Regards, Niklas
>



--=20
Silvio Mariji=C4=87
Software Engineer
2e Systems

--089e010d871458efe4053c13fd0d--