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-proxy-interceptor

v0.8.7

Published

middleware for node-http-proxy to modify responses using streams

Downloads

157

Readme

http-proxy-interceptor Build Status

http-proxy-interceptor is a middleware for node-http-proxy that modifies responses using streams

Installation

npm install http-proxy-interceptor

Usage

httpProxyInterceptor(interceptorFactory[, filter])

interceptorFactory is a required callable that receives two arguments (req and res) and should return a Transform Stream. This stream receives and transforms the http response body. interceptorFactory can also return an Array of Transform Streams. In this case, the constituent streams will be turned into a pipe chain, with the first array element being first in the chain, etc.

filter is an optional Object with one or two properties:

  • url: a RegExp against which request URL's are tested. Only responses whose request URL matches get intercepted
  • headers: an Object whose keys are header names and values are RegExp's against which the response headers are tested. Only responses where all of the headers match are intercepted. If any of the specified filter headers do not exist in the response, the match fails.

If no filter is passed, all responses are intercepted.

Example

const connect = require('connect')
const http = require('http')
const httpProxy = require('http-proxy')
const httpProxyInterceptor = require('http-proxy-interceptor')

var interceptorFactory = function(req, res) {
    //Use different streams depending on the request
    if (/\.css$/.test(req.url))
        return new cssModifyingStream()
    else
        return [new otherModifyingStream(), new otherModifyingStream(withArguments)]
}

const filter = {
    url: /\/\w+/, //Only match non-root requests
    headers: {
        'content-type': /text/ //Only match requests that specify text-based content types
    }
}

const port = 8000
const options = {
	target: "https://nodejs.org/",
	changeOrigin: true,
	hostRewrite: `localhost:${port}`,
	protocolRewrite: "http",
	cookieDomainRewrite: "localhost"
}

var proxy = httpProxy.createProxyServer(options)
var app = connect()
app.use(httpProxyInterceptor(interceptorFactory, filter))
app.use(function(req, res) {
    proxy.web(req, res)
})
var server = http.createServer(app).listen(port)

Also see examples

Notes

The middleware handles gzip and deflate compression automatically, based on the Content-Encoding header in the response. The http response is passed through a decompression stream before arriving at the intercepting transform stream, and through a compression stream before being sent to the next middleware.

Because transform streams (and compression) can arbitrarily change the response length, a fixed Content-Length header will not work. If one exists, the middleware will remove it. The middleware always usesTransfer-Encoding: chunked.

License

The MIT License (MIT)

Copyright (c) 2018 Aram Akhavan

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.