npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

http-api-proxy

v1.0.0

Published

A reverse proxy designed for use with rate limited APIs.

Downloads

1

Readme

node-api-proxy

A reverse proxy designed for use with rate limited APIs.

Installation

npm install http-api-proxy

Usage

Any requests to the proxy must have the Host header set to the upstream host. Any requests to an upstream host that the proxy has not been configured for will return errors unless a default interval is set.

To start a proxy:

http-api-proxy -c <config-file.json>

If the config file is not specified, it defaults to ~/.config/http-api-proxy/config.json (or the appropriate value if you've set $XDG_CONFIG_HOME).

The config file should be a JSON file with the following properties:

  • httpPort: The port on which the HTTP proxy server should listen. The server on this port will only proxy sites where the protocol is HTTP.
  • httpsPort (optional): If set, listen on this port and proxy sites where the protocol is HTTPS. Note that the proxy server itself still uses HTTP rather than HTTPS.
  • sites: A list of sites that the proxy can delegate requests to. If a request is made for a site that is not referenced here, the proxy will respond with a 500 error. Each element should have the following properties:
    • upstream: The host for the upstream site, such as http://example.com or http://example.com:8080.
    • interval: Ensure that at least interval milliseconds elapse between each request to this site.
  • cacheAge (optional): If set, successful GET requests will be cached for cacheAge milliseconds.
  • cachePath (optional): If set, the specified path will be used to persist the cache.
  • defaultInterval (optional): If set, any requests to an upstream host that have not been explicitly configured will use this value for interval.

Examples

Suppose you want to access a particular API at most once per second:

http-api-proxy -c config.json

where config.json looks like:

{
    "sites": [
        {
            "upstream": "http://example.com",
            "interval": 1000
        }
    ],
    "httpPort": 8080
}

Then, to use the proxy:

curl http://localhost:8080/ -H"Host: example.com"

If you wanted to also proxy a site that is served over HTTPS:

{
    "sites": [
        {
            "upstream": "http://example.com",
            "interval": 1000
        },
        {
            "upstream": "https://secret.example.com",
            "interval": 1000
        }
    ],
    "httpPort": 8080,
    "httpsPort": 8081
}

And to use the proxy:

curl https://localhost:8081/ -H"Host: secret.example.com"