Service discovery + error: real URL not in exception

We use service discovery in our apps. It works perfectly—as long as the URL is correct. However, if an incorrect URL is specified in the configuration, the exception simply returns a 404 error and displays the configured service discovery URL (such as https://myurl), not the actual URL that was called. This is very confusing when an error occurs: First, I have to check: Is my Service Discovery implemented correctly? Then I have to check the configuration and realize that the URL was set up incorrectly.
QUESTION: Why can't the exception simply display the actual URL (resolved by service discovery) that was ultimately used (as in a REST call)? That would be a big help.
Thank you.