Adding entry into host header settings in the web.config file isn't flowing through into the application, and the wrong url is being used for package URL's, etc.
So heading to the http://proxyurl.com/chocolatey will show the NuGet api xml with the original url in it, and if you head to the packages page, they do the same.
Adding entry into host header settings in the web.config file isn't flowing through into the application, and the wrong url is being used for package URL's, etc.