You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 8, 2019. It is now read-only.
I should be able to specify a scheme and url path for a service address in consul, for instance
"address": "http://mydomain.com/MyService/",
This is valid consul configuration (although I appreciate that it might not be a common way of configuring consul), as we are using it in production at the moment.
Actual Behaviour
I get an error:
to use service Address: http://mydomain.com/MyService/ and Port: 80 as it is invalid. Address must contain host only e.g. localhost and port must be greater than 0
Steps to Reproduce the Problem
Register a service in consul with an address similar to above.
Register consul in ocelot, similar to below
@dimitridaras thanks for your interest in the project, I would suggest easiest way to get this would be fork Ocleot.Provider.Consul and make your change. Implementing it in Ocelot will be a faff because Ocelot only expects to get host and port from consul not the path / scheme. That would need some kind of change. I will leave this issue open and might get round to doing it one day.
Expected Behaviour
I should be able to specify a scheme and url path for a service address in consul, for instance
"address": "http://mydomain.com/MyService/",
This is valid consul configuration (although I appreciate that it might not be a common way of configuring consul), as we are using it in production at the moment.
Actual Behaviour
I get an error:
to use service Address: http://mydomain.com/MyService/ and Port: 80 as it is invalid. Address must contain host only e.g. localhost and port must be greater than 0
Steps to Reproduce the Problem
Register a service in consul with an address similar to above.
Register consul in ocelot, similar to below
Specifications
Thanks!
The text was updated successfully, but these errors were encountered: