Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NuGet API does not respect UseHostHeaderForRequestUrl - Unable to use a Proxied Url for any requests through that #44

Open
gep13 opened this issue Apr 18, 2018 · 1 comment
Open

NuGet API does not respect UseHostHeaderForRequestUrl - Unable to use a Proxied Url for any requests through that #44

gep13 opened this issue Apr 18, 2018 · 1 comment
Labels
bug customer

Comments

@gep13
Copy link
Member

gep13 commented Apr 18, 2018

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.
@ferventcoder ferventcoder changed the title Proxy Issue UseHostHeaders is not respected for NuGet Api when added to web.config - proxied urls error Apr 18, 2018
@ferventcoder ferventcoder changed the title UseHostHeaders is not respected for NuGet Api when added to web.config - proxied urls error NuGet API does not respect UseHostHeaderForRequestUrl - Unable to use a Proxied Url for any requests through that Apr 18, 2018
@ferventcoder
Copy link
Contributor

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.

ferventcoder added a commit that referenced this issue Apr 18, 2018
@ferventcoder
(GH-44) add aspnet:UseHostHeaderForRequestUrl to config
2443a0f 
Add this to ensure that it would use whatever the host header is to
produce the url portions of the requests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug customer
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ferventcoder @gep13