[Bug] not working at node 17
See original GitHub issueChecks
- I understand project setup issues should be asked on StackOverflow or in GitHub Discussions.
- I updated to latest
http-proxy-middleware
.
Describe the bug (be clear and concise)
use the library to proxy into another service. not working when upgraded to node 17.
Step-by-step reproduction instructions
1. using node 14.17 - works.
2. replace node 17.x - doesn't work.
console error:
[HPM] Error occurred while proxying request localhost:3000/aaa/ to http://localhost:3001/ [ECONNREFUSED]
### Expected behavior (be clear and concise)
proxy should work and return the data from another proxied service
### How is http-proxy-middleware used in your project?
```shell
└── http-proxy-middleware@2.0.2
What http-proxy-middleware configuration are you using?
{
target,
changeOrigin: true,
headers: {
tenant,
},
}
What OS/version and node/version are you seeing the problem?
System:
OS: macOS 12.1
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 492.53 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 17.4.0 - ~/.nvm/versions/node/v17.4.0/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 8.3.1 - ~/.nvm/versions/node/v17.4.0/bin/npm
Watchman: 2021.10.18.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /Users/XXX/.rvm/rubies/ruby-head/bin/pod
Homebrew: 3.3.9 - /usr/local/bin/brew
pip3: 21.2.4 - /usr/local/bin/pip3
RubyGems: 2.7.6 - /Users/XXX/.rvm/rubies/ruby-head/bin/gem
Utilities:
CMake: 3.16.4 - /usr/local/bin/cmake
Make: 3.81 - /usr/bin/make
GCC: 4.2.1 - /usr/bin/gcc
Git: 2.32.0 - /usr/bin/git
Clang: 13.0.0 - /usr/bin/clang
Servers:
Apache: 2.4.51 - /usr/sbin/apachectl
Virtualization:
Docker: 20.10.12 - /usr/local/bin/docker
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
IDEs:
Nano: 2.0.6 - /usr/bin/nano
Vim: 8.2 - /usr/bin/vim
WebStorm: 2021.3.1
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Bash: 3.2.57 - /bin/bash
Perl: 5.30.3 - /usr/bin/perl
Python: 2.7.18 - /usr/bin/python
Python3: 3.9.7 - /usr/local/bin/python3
Ruby: 2.6.0 - /Users/XXX/.rvm/rubies/ruby-head/bin/ruby
Databases:
MongoDB: 4.2.1 - /usr/local/bin/mongo
PostgreSQL: 14.0 - /usr/local/bin/postgres
SQLite: 3.36.0 - /usr/bin/sqlite3
Browsers:
Chrome: 97.0.4692.99
Firefox: 57.0.4
Safari: 15.2
Additional context (optional)
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:19 (12 by maintainers)
Top Results From Across the Web
Node.js v19.3.0 Documentation
Bugs found in legacy features are unlikely to be fixed. Use caution when making use of Experimental features, particularly within modules. Users may...
Read more >15 Common Error Codes in Node.js and How to Fix Them
The fix for this problem is to ensure that the target service is active and accepting connections at the specified endpoint. 5.
Read more >The Journey About How I Fixed a Bug in the Node.js Core ...
In this talk, I'll dig into the process from opening and discussing an issue, to implementing a new feature on the Node.js core....
Read more >Node.js 17 Reached EOL: What Does That Mean for You?
Your installation will always be vulnerable to security issues fixed in later versions. · You're stuck with any bugs your current installation ......
Read more >Top 10 Most Common Node.js Developer Mistakes - Toptal
In many asynchronous functions, the return value has almost no significance, so this approach often makes it easy to avoid such a problem....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You shouldn’t be using
localhost
but127.0.0.1
instead. Reason is that name resolution for localhost varies a lot between different systems and implementations of their network stacks.Yes, partly. It just doesn’t reorder the DNS results anymore. That’s what we said all the time. The lookup works the same as before. Don’t use the DNS flag as it will prevent IPv6-connectivity. Just instead of localhost use 127.0.0.1.