Home Issue with .NET Core routing while running microservice under mydomain.com/service
Reply: 0

Issue with .NET Core routing while running microservice under mydomain.com/service

M U
1#
M U Published in 2017-12-07 23:42:25Z

I am starting to slowly deploy my services to test server. It was working nice locally as each service is binded to separate port 5001/5002/...

On the server I am using Traefik as proxy to forward requests to appropriate service. I have started deploy from AuthService which should be available under mydomain.com/auth/*(service routes). However it is not working with routing.

My service thinks it is on the mydomain.com and /auth is just part of route.

I have tried to set up redirect from home to /swagger (docs available easily for frontend dev) but it then redirect to mydomain.com/swagger instead of mydomain.com/auth/swagger.

What do I have to do? I would prefer not to bind each service to subdomain as it will become really inconvenient for frontend devs. Is it possible to somehow make my service use mydomain.com/auth as baseUrl?

You need to login account before you can post.

About| Privacy statement| Terms of Service| Advertising| Contact us| Help| Sitemap|
Processed in 0.358188 second(s) , Gzip On .

© 2016 Powered by mzan.com design MATCHINFO