Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New features and enhancements #5

Merged
merged 7 commits into from Feb 9, 2012
Merged

Conversation

fdmanana
Copy link
Contributor

Hi,

I've been integrating lhttpc with Apache CouchDB (to replace ibrowse), but it lacked a few features that are currently supported by ibrowse. This pull requests adds those features and enhances the httpc connection pool (so that it can replace the custom one from CouchDB).

I also made a pull request to Oscar, but it's been a long time and got no feedback:

oscarh/lhttpc#3

thanks

Also enhanced the lhttpc_lib:parse_url/1 to parse
credentials as specified in RFC1738 - before if user
credentials were specified, this function would consider
that what follows the first : is the port and not a
password.
If an URL targets an IPv6 host, lhttpc will now pass the
inet6 option to the socket automatically.
This also fixes 2 bugs:

1) in lhttpc_lib:parse_url/1 when the host component is an IPv6
   address literal - the parser thinks that what follows the
   first : is a port number;

2) for IPv6 address literals, the Host header must surround those
   literals in square brackets (RFC2732)
This change adds support for HTTP proxies that allow the HTTP
CONNECT method tunneling [1, 2]. Tested against Squid 3.1.15.

[1] http://muffin.doit.org/docs/rfc/tunneling_ssl.html
[2] http://tools.ietf.org/html/rfc2817
This allows the connection pool (lhttpc_manager) to
block clients, when they request a socket, when the
current number of open sockets/connection reaches a
certain (configurable) threshold.
This test verifies that the lhttpc_manager pool closes sockets
if they are not used after a configurable period of time.
This change allows different clients to use different connection
pools (lhttpc_manager instances). This is useful when we have
several different applications or process groups which are
independent and shouldn't share the same pool.
It also reduces the overhead of messaging a single centralized pool.
This helps better identifying which tests fail and
give a notion of progress/staleness.
paulgray added a commit that referenced this pull request Feb 9, 2012
New features and enhancements
@paulgray paulgray merged commit 1b3457e into esl:master Feb 9, 2012
rymir pushed a commit to rymir/lhttpc that referenced this pull request Mar 11, 2013
g-andrade pushed a commit to g-andrade/lhttpc that referenced this pull request Nov 26, 2014
Use os:timestamp instead of erlang:now for link expiration
g-andrade pushed a commit to g-andrade/lhttpc that referenced this pull request Nov 26, 2014
GetEndpointAttributes implementation
massemanet pushed a commit to campanja-forks/lhttpc that referenced this pull request Mar 9, 2017
Merge me - combination of two previous PR
g-andrade added a commit to g-andrade/lhttpc that referenced this pull request Aug 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants