Nick Wesselman
Nick Wesselman
This appears to be an issue with `node-http-proxy`, and the fact that it [uses `.on('socket')` to fire the `proxyReq` event](https://github.com/http-party/node-http-proxy/blob/master/lib/http-proxy/passes/web-incoming.js#L131). This took a lot of digging into the behavior of...
Workaround we've found is to instead modify the request headers in separate middleware, before applying the proxy. ``` server.use((req, res, next) => { // change req here next(); }); ```
We have a standard project structure that results in Rust packages two levels deep, and thus not working with Rust Analyzer. `linkedProjects` is a workaround but requires configuring each package...
Hey @jasonjohnlee, Instead of adding the port number to the `hostName` attribute, can you try adding a `port` attribute? Otherwise, I'd agree with the StackExchange answer, except instead of manually...
@jasonjohnlee Not on SDN but I'm looking at the Kernel code right now and it's there. :) Can you see if it solves for you?
@rupa29 Our product team, who supports GitHub issues, can't do calls. Perhaps you could reproduce the issue in a simpler, non-customer codebase which you are able to share? Otherwise you...
@rupa29 Were you able to resolve this?
@rupa29 Can you provide the internal ticket # so we can reference?
@rupa29 Looks like we are still awaiting a sample that demonstrates the issue there as well.
I've just been making feature branches off of `master`. Given the plans to retire Habitat after 9.2, is this worth the effort?