Aaron
^ part of what will be the release including #1995; no hard dates yet, but getting closer
whoa, updating the testing artifacts added a bunch of folks as reviewers; I'm still figuring out how to work in the router repo, so ignore this pr for now (making...
@lennyburdette: mmm, rebased, but not sure why there are mdx changes in the diff (unless you added them before?)
when I return to this branch, I'll track down what happened; I'll rebase them away if they're not from you, otherwise I'll just keep rebasing via the github UI and...
@abernix: I haven't had time to rebase, and I still need to get some changes sorted/pushed (filtering what we send back--have something in the right direction, but it's not complete...
thanks for raising this; we've been looking into it and related issues!
@yliu-intuit: this makes sense; let me validate it and respond in a bit! thanks for opening a pr
alas, I wasn't able to repro the error--it seems to work for me, but that doesn't mean it actually works, it'd be nice to see it working for you here's...
ohhh, yeah, interesting; without upgrading, maybe there's something there that's breaking (I've been kind of worried about the `serve_connection_with_upgrades`, but it predates the http2 header config change and I haven't...
[retrying with that curl and config doesn't quite do the dirt](https://www.loom.com/share/6e55c56005b3430da3b9d7dac718dce5); so, I'm wondering if your router isn't getting the right config? It's hitting the default header size limit from...