Adding a repository to the chain of the Virgo instance which is acting as a repository server does not make that repository externally visible as a URL. The contents of the added repository will be available via the normal remote repository URL.
So I'd be very surprised if you ever saw the 2.1.1 behaviour you describe. Perhaps it is worth checking the rest of your 2.1.1 configuration to make sure somebody didn't sneak in some extra configuration that you are not aware of.
Maybe that's the case, I will start with a fresh virgo 2.1.1 just to be sure.
With virgo 2.1.1 accessing the adress start the download of an xml file. With virgo 3.0.2 I get a 404 error with the browser and there is the same 404 error in the log file of the remote repository, so I guess the problem is with my hosted repository.
I made some tests starting with fresh download of virgo 2.1.1. and virgo 3.0.2. With virgo 2.1.1, no problem the hosted repository work fine and is accessible just by adding some bundles in the folder repository/hosted. With virgo 3.0.2 I am still getting a 404 error... For now I will go in production with virgo 2.1.1 as the hosted repo and will investigate further my problem with virgo 3.0.2 in the next month.
Thanks Anton. That behaviour is consistent with the behaviour reported by jc perron above. But I'm not convinced that this should ever have worked as adding a repository to the chain of the Virgo instance which is acting as a repository server does not make that repository externally visible as a URL. I asked jc perron whether this used to work on 2.1.1, which would be most surprising, but I am still waiting for a response. Do you have an answer to that?
Anyway, a 404 of that URL is no indication of a problem. You should still be able to configure another Virgo instance to use a remote repository by following the information in the User Guide.
I think the bottom line here is that if hosted repositories are not working properly, a bug should be raised with details of how to reproduce the problem so a fix can be investigated. I'm afraid the invalid URLs posted early in the thread have been a bit of a distraction from the real issue.