Applying resources to another port

[Bobby Johansen]

Hi all, I am trying to provide a layer of security for my team by implementing an easy way to create Internal API Resources. I was hoping to bind the API resources to another port so that we could expose only the default 8080 resources and internally expose other resources on say 8082 (not the admin port). Has anyone run into this before? Am I way off base here?

[Leonardo Contreras Alfonso]

I had the same idea 2 years ago, it's not straight forward with dropwizard, you would have to deal with jetty directly to do this. My solution was to place a reverse proxy in front of my app that rewrites every request adding an '/api' prefix, the endpoints I need to be private (inside my k8s), use different prefixes. It's enough for my case, not sure if it could work for you.

On Fri, Dec 27, 2019 at 2:43 PM Bobby Johansen <bobby.j...@gmail.com> wrote:

Hi all, I am trying to provide a layer of security for my team by implementing an easy way to create Internal API Resources. I was hoping to bind the API resources to another port so that we could expose only the default 8080 resources and internally expose other resources on say 8082 (not the admin port). Has anyone run into this before? Am I way off base here?

--
You received this message because you are subscribed to the Google Groups "dropwizard-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dropwizard-user/133213fa-0a4e-4b2c-a5a1-6031c1d5cc56%40googlegroups.com.

--

-----------------------------------------------------------
Leonardo Contreras Alfonso
Bogotá D.C. - Colombia