Jason Hoetger

I think this is a great idea! It's slightly more complicated than you'd think, because of the way LittleProxy's filters and filter factories work. I've also considered perhaps having the...

Are there any URLs you're hitting that we can test against? That'll help determine the source of the problem. Just FYI, don't address issues to specific people. Anybody who's monitoring...

@tlytvyn What issue are you having? An empty HAR indicates that the browser is not configured properly to send traffic to BMP.

Are you seeing any error in the browser, or just not seeing any entries for https? Browsers have both an http and an https proxy setting, so make sure you're...

HTTP/2 is one of the compelling reasons for the shift to LittleProxy. Once LittleProxy supports HTTP/2, BMP will be able to support it with (hopefully) little modification. So, long story...

I'd like to keep this issue open, to track our HTTP/2 implementation status. It might not be "soon", depending on your definition of soon, but it will be as soon...

No ETA at this time. It's a large undertaking. Now that MITM has been released, this is the "next big thing", but it's still a few months away.

Yes, you've found an unfortunate limitation of BMP that stems from LittleProxy's ConnectionFlow. There's a refactor of CF in the works that will solve this problem, but it won't be...

Not yet, unfortunately. I'm on the verge of releasing the next version of the REST API for comment. ConnectionFlow refactor is the next big thing on my list though.

I just ran into this issue, seeing the same peer dependency warnings as @rossng. Using the `peerDependenciesMeta` field of package.json might be a good solution: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#peerdependenciesmeta Adding this to package.json...