Bug: Failed to load service intercept configuration

[Wbeggin]

When going from a service to that service's intercept configuration (or host), it often fails to load. The same thing does not happen when you go from the configurations list to the same configuration.

Analysis of Differences

Here's a summary of the differences in the generated links:

Source	Tag Structure	Href Format	Classes/Attributes
Service → Config	<div><strong>	.//configs/...	col cell-name-renderer, id
Configurations Tab	<span>	./configs/...	mat-mdc-tooltip-trigger, ARIA, etc.

• Href Format: The href from the service detail page starts with .//configs/..., while the one from the configurations tab starts with ./configs/.... The double slash is unusual.

These differences, especially in the href format and the component structure, could affect how Angular's router interprets the navigation and loads the associated component. The double slash in the href from the configurations tab is particularly suspicious.

[rgallettonf]

That double slash in the href is definitely a little concerning and indicates something is off with the link creation logic in the service details component. However I'm not able to reproduce the issue of the config not loading, even when navigating using the link with the double slash. Regardless I will take a look and see if we can clean that link up to be consistent with how the configurations page defines it. Hopefully that will resolve the issue for you.

[Wbeggin]

Thanks for the quick response and for investigating the link creation logic.

I should have mentioned that my connection to the ZAC has high latency, with a round trip ping of about 300ms. This might be why you're unable to reproduce the config loading issue on your end.

Let me know if you'd like me to run any other tests from my side. I'm hopeful that cleaning up the link will fix the problem since I don't experience the issue anywhere else.