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_trace

v0.5.0

Published

Live HTTP packet capture and protocol decoding

Downloads

5

Readme

examples/http_trace

This is a handy program that decodes HTTP and WebSocket traffic. It uses node_pcap. Install it with:

npm install http_trace

Usage http_trace [options]

Capture options:
    -i <interface>           interface name for capture (def: first with an addr)
    -f <pcap_filter>         packet filter in pcap-filter(7) syntax (def: all TCP packets)
    -b <buffer>              size in MB to buffer between libpcap and app (def: 10)

HTTP filtering:
    Filters are OR-ed together and may be specified more than once.
    Show filters are applied first, then ignore filters.
    --method <regex>            show requests with this method
    --method-ignore <regex>     ignore requests with this method
    --host <regex>              show requests with this Host header
    --host-ignore <regex>       ignore requests with this Host header
    --url <regex>               show requests with this URL
    --url-ignore <regex>        ignore requests with this URL
    --user-agent <regex>        show requests with this UA header
    --user-agent-ignore <regex> ignore requests with this UA header

HTTP output:
    --headers                print headers of request and response (def: off)
    --bodies                 print request and response bodies, if any (def: off)
    --tcp-verbose            display TCP events (def: off)
    --no-color               disable ANSI colors (def: pretty colors on)

Examples:
    http_trace -f "tcp port 80"
       listen for TCP port 80 on the default device
    http_trace -i eth1 --method POST
       listen on eth1 for all traffic that has an HTTP POST
    http_trace --host ranney --headers
       matches ranney in Host header and prints req/res headers

Screenshot

http_trace screenshot

The TCP tracker in node_pcap looks for HTTP at the beginning of every TCP connection. If found, all captured data on this connection will be fed to node's HTTP parser and events will be generated. http_trace has listeners for these events and will print out some helpful information.

If a WebSocket upgrade is detected, http_trace will start looking for WebSocket messages on that connection.