You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently ran into a case where I had to upgrade the `http-proxy` version for an app, and that app was using a proxy table.
I'm not sure how many users are still using the 0.x.x version of `http-proxy`, but the added link (found from one of the GH issues) may encourage them to switch over to 1.x.x if they were using the old version due to its proxy table support and the activation energy to upgrade was too high.
I might release a module for this eventually, lol, since there was some work involved in creating a proxy table to map paths to paths for the same hostname.
Copy file name to clipboardExpand all lines: UPGRADING.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -92,5 +92,6 @@ which were in the core and delegate them to eventual "userland" modules.
92
92
93
93
The new API makes it really easy to implement code that behaves like the old Middleware API. You can check some examples [here](https://github.com/nodejitsu/node-http-proxy/tree/caronte/examples/middleware)
94
94
95
+
### ProxyTable API
95
96
96
-
97
+
See this [link](http://blog.nodejitsu.com/node-http-proxy-1dot0/) for an example of how to add proxy table functionality using the new API.
0 commit comments