[Fwd: HTTP error codes mandated by the specs and library's OAuthException]

9 views
Skip to first unread message

Olivier Berger

unread,
Mar 28, 2011, 4:49:26 PM3/28/11
to oaut...@googlegroups.com
Hi.

I may have mistakenly sent my post to the wrong list, so here we
go again :

-------- Message transféré --------
De: Olivier Berger <olivier...@it-sudparis.eu>
À: OAuth <oa...@googlegroups.com>
Sujet: [PHP] HTTP error codes mandated by the specs and library's
OAuthException
Date: Mon, 28 Mar 2011 01:09:48 -0700 (PDT)

Hi.

We're using the OAuth PHP library (developing a FusionForge OAuth
provider plugin), and I've noticed there seems to be no handling of
error conditions, but through strings passed to OAuthException
triggered in case of errors, that'd allow to easily handle them and
return 400 or 401 HTTP return codes (as mandated by specs 1.0).

I'm tempted to introduce such a fix through patches, but if someone
has already done so, I'd be curious to know ;)

Thanks in advance.

Best regards,

--
Olivier BERGER <olivier...@it-sudparis.eu>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)

Olivier Berger

unread,
Mar 28, 2011, 4:52:36 PM3/28/11
to OAuth PHP
Oh, and btw, here's my proposed patch (as applying to Debian package's
version): http://code.google.com/p/oauth/issues/detail?id=48#c4

Hope this helps.

Best regards,

On Mar 28, 10:49 pm, Olivier Berger <olivier.ber...@it-sudparis.eu>
wrote:
> Hi.
>
> I may have mistakenly sent my post to the wrong list, so here we
> go again :
>
> -------- Message transféré --------
> De: Olivier Berger <olivier.ber...@it-sudparis.eu>
> À: OAuth <oa...@googlegroups.com>
> Sujet: [PHP] HTTP error codes mandated by the specs and library's
> OAuthException
> Date: Mon, 28 Mar 2011 01:09:48 -0700 (PDT)
>
> Hi.
>
> We're using the OAuth PHP library (developing a FusionForge OAuth
> provider plugin), and I've noticed there seems to be no handling of
> error conditions, but through strings passed to OAuthException
> triggered in case of errors,  that'd allow to easily handle them and
> return 400 or 401 HTTP return codes (as mandated by specs 1.0).
>
> I'm tempted to introduce such a fix through patches, but if someone
> has already done so, I'd be curious to know ;)
>
> Thanks in advance.
>
> Best regards,
>
> --
> Olivier BERGER <olivier.ber...@it-sudparis.eu>http://www-public.it-sudparis.eu/~berger_o/- OpenPGP-Id: 2048R/5819D7E8
Reply all
Reply to author
Forward
0 new messages