|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #62485 Support HTTP Keep-Alive
Submitted: 2012-07-05 18:52 UTC Modified: 2012-07-16 15:51 UTC
Avg. Score:4.0 ± 1.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:1 (100.0%)
From: andrew at pimlott dot net Assigned:
Status: Open Package: oauth (PECL)
PHP Version: 5.3.14 OS: Debian Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: andrew at pimlott dot net
New email:
PHP Version: OS:


 [2012-07-05 18:52 UTC] andrew at pimlott dot net
The OAuth library opens a new HTTP connection for every ->fetch call.  In many 
cases it would be a significant optimization to reuse connections with HTTP Keep-
Alive.  Any developer interested in implementing this?  I care more about the 
cURL back-end than streams.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2012-07-05 19:04 UTC]
Is there really much point in that? OAuth1 is disappearing quickly and you don't 
need an extension because unlike OAuth1, OAuth2 is trivial to implement in 
 [2012-07-16 15:51 UTC] andrew at pimlott dot net
Sorry for the slow reply....  I didn't know much about OAuth1 vs OAuth2 or Oauth1 
disappearing, but I am looking into it with regard to the API I'm using 
(LinkedIn).  (They support OAuth2 but imply it is only for their JavaScript API 
and don't document how to use it directly.  I will try to figure it out.)

Thanks for the pointer!
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat May 18 02:01:33 2024 UTC