Missing of headers support on UMF messages affecting hydra-router response on legacy environments about hydra-router HOT 5 CLOSED

@jkyberneees I'm doing some cleanup on Hydra-Router that will make this an easier conversation to have. Specifically, the HydraRouter routeRequest function is too large and in need of refactoring. Feedback on your points above to follow...

from hydra-router.

Great, I keep an eye on this.

from hydra-router.

@jkyberneees please see if hydra-router 1.3.1 addresses this issue. Also requires that the service themselves using the latest hydra / hydra-express as updates are in makeAPIRequest.

from hydra-router.

@cjus Hi Carlos, thanks for taking care of the issue/feature/suggestion.
I reviewed the code and I see that you inject the request headers and consider the response too, however I don't understand this exclusion: https://github.com/flywheelsports/hydra/blob/master/index.js#L1103

Unfortunately, the feature is not yet working as expected, since hapi services are still not properly routed ;(
Let me know if you need more details to reproduce.

Best Regards, Rolando

from hydra-router.

@jkyberneees the line you referenced checks whether instanceList.length is zero - if that's the case then there are no more service instances to try so a service unavailable response is necessary. The 1.3.1 release was found to have problems - please see if the issue is resolved in hydra-router:1.3.8

from hydra-router.