How do I proxy _some_ requests to '/' using http-proxy-middleware for Webpack?

Question

I'm trying to solve a unique problem w/ an app where I need to use webpack dev-server's proxy functionality to proxy specific requests through to a backend service.

The problem I'm having is figuring out how to handle an odd use case.

I have Webpack DevServer (WDS) serving up my index.html for a Single Page App w/ multiple client-side routes. The SPA makes clientside AJAX/fetch requests to different endpoints that need to be proxied. Unfortunately, one of the endpoints is / on the server but only for requests w/ a specific Content-Type header (I can't change the path this service is listening on, so adding some kind of path-prefix is not an option here).

I've tried using the bypass option in my WDS config to do something like this:

proxy: {
        "/": {
          target: "http://ows.local:6273",
          logLevel: "debug",
          secure: false,
          bypass: (req) => {
            console.log(`req.path => `, req.path)
            if (req.headers.accept.indexOf('html') !== -1) {
              console.log('Skipping proxy for HTML request.')
              return 'src/index.html'
            }
            return null
          }
        }
      }

The problem arises w/ initial calls for HTML, that which WDS should be serving up w/ the compiled .js and .css bundles injected. All I get is the base src/index.html w/o the injected assets (no injected <script> tags). This makes sense because I know I'm telling the proxy here, "Don't proxy this request to the target, just serve up the contents of this file", but that's not what I want. I need the compiled index.html that WDS serves as default, w/ the injected assets.

So here's my question w/ some specificity:

How can I essentially tell the proxy, "For requests that have Content-type: application/json(or whatever), go ahead and proxy them through to the target, but for calls for HTML, don't proxy then, just serve up the WDS-compiled index.html"?

You should be able to do this on the frontend without any hazzle. I'd check the back-end proxy and filter out requests there instead to see if the problem is with the proxy or wds, if that makes sense — Even Stensberg
– Even Stensberg, Commented Dec 23, 2019 at 18:44

RavenHursT · Accepted Answer · 2019-12-24 00:36:12Z

2

Turns out, all it took to solve this was to adjust the return value of the bypass() function.

proxy: {
        "/": {
          target: proxyTargetUtl,
          secure: false,
          logLevel: "debug",
          bypass: (req) => (req.headers.accept.includes("html") ? "/" : null)
        }

answered Dec 24, 2019 at 0:36

RavenHursT

2,3541 gold badge28 silver badges50 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

How do I proxy _some_ requests to '/' using http-proxy-middleware for Webpack?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related