Skip to content
This repository has been archived by the owner on Jan 3, 2018. It is now read-only.

Proxy contexts don't trigger #7

Closed
ivern opened this issue May 14, 2015 · 3 comments
Closed

Proxy contexts don't trigger #7

ivern opened this issue May 14, 2015 · 3 comments
Assignees

Comments

@ivern
Copy link
Contributor

ivern commented May 14, 2015

Using the following configuration:

servers: {
  web: {
    host: '0.0.0.0',
    port: 8090
  },
  aries: {
    port: 8280,
    proxy: true,
    proxies: [
      {
        context: "/api",
        rewrite: {
          from: "^/api",
          to: ""
        }
      },
      {
        context: "/public/api",
        rewrite: {
          from: "^/public/api",
          to: ""
        }
      }
    ]
  },
  axi: {
    port: 8080,
    proxy: true,
    proxies: [
      {
        context: "/availity"
      }
    ]
  }
}

}

I can't get the proxy routes to fire. What appears to be happening is that by the time proxy.js gets the request URL to process, req.url already has the context stripped. It's getting /v1/blah instead of /api/v1/blah, which means the matcher never fires.

@robmcguinness
Copy link
Contributor

@robmcguinness
Copy link
Contributor

@ivern have you tried the latest version?

@KaseyPowers
Copy link
Contributor

I believe this has been fixed, if it is still occurring please reopen.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants