http-proxy-middleware VS grupo

Then we translate each rule. webpack-dev-server uses http-proxy-middleware under the hood, and here's how to translate each field.

Oh and you might wanna take a look at the github for the proxy middleware library under the ECONNREFUSED section

Actually I'm receiving errors like The resource from “http://localhost:8090/Sidebar/Sidebar.css” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff)... Both my css and js files are gettings "text/html" on their headers and changing the http-proxy-middleware options doesn't seem to change it... On their GitHub there's an issue about it: https://github.com/chimurai/http-proxy-middleware/issues/580 ... And they say that it's a webpack issue: https://github.com/froala/angular-froala/issues/170 ... But these solutions on the second page don't work for me.

// Create a proxy to redirect requests of the "/api/*" path to "https://example.org". // // Examples: // GET /api/hello → GET https://example.org/hello // POST /api/test?color=red → POST https://example.org/test?color=red // // Additionally, the proxy will: // - Add an "x-added" header // - Remove the "x-removed" header // From the proxied response. // // You can/should update the proxy to suit your needs. // See https://github.com/chimurai/http-proxy-middleware for more details. const { createProxyMiddleware } = require('http-proxy-middleware'); const apiProxy = createProxyMiddleware({ target: "https://example.org", changeOrigin: true, pathRewrite: { "^/api": "" // strip "/api" from the URL }, onProxyRes(proxyRes) { proxyRes.headers['x-added'] = 'foobar'; // add new header to response delete proxyRes.headers['x-removed']; // remove header from response } }); // Expose the proxy on the "/api/*" endpoint. export default function (req, res) { return apiProxy(req, res); };