Improve feedback when GN cannot connect to service if not logged in about core-geonetwork

[fxprunayre]

Not sure how we could improve this. It relates to the fact that the proxy is by default not permissive and only allows URL found in metadata records (cf. https://docs.geonetwork-opensource.org/4.2/maintainer-guide/production-use/#web-proxy) but the scan of URL is only triggered manually - maybe we should make it more regular/automatic?

[GeoSander]

@fxprunayre To be clear: I am not asking to change behavior, just the message. :)

But looking at the WfsDirective.js I see that there indeed is no way to tell why the WFS GetCapabilities failed, so it's hard to provide a correct feedback message like that.

I haven't looked or tried yet, but do you know if the responses of the WFS GetCapabilities request in the OWSService.js are different if:

• the user is not logged in (anonymous);
• the user is logged in and the URL exists (200);
• the user is logged in and the URL does not exist or is unreachable (i.e. 404 or timeout)?

If there is a distinction, I guess we can provide a correct feedback message to the user.
Something along the lines of:

• anonymous users -> "Please log in to connect to the service"
• logged in but no or bad response -> "Unable to connect to the service"

Do I make sense?