[Bug?] Headers lost

[ferventcoder]

It appears I am losing headers now that I am using this...

X-NuGet-ApiKey: thekey <- I replaced the actual guid with thekey in this issue report only. The actual request makes use of a real key.

Request:

PUT http://chocotest.apphb.com/api/v2/package/ HTTP/1.0
User-Agent: NuGet Command Line/1.6.21205.9031 (Microsoft Windows NT 6.1.7601 Service Pack 1)
X-NuGet-ApiKey: thekey
Content-Type: multipart/form-data; boundary=---------------------------8cf71b7537342b2
Host: chocotest.apphb.com
Content-Length: 3723

I left out the rest of the request

Response:

HTTP/1.1 400 The API key '' is invalid. <- It looks like it is losing the key that is passed to it in the headers

HTTP/1.1 400 The API key '' is invalid.
Server: nginx
Date: Sat, 06 Oct 2012 13:54:58 GMT
Content-Type: text/html
Connection: close
Cache-Control: private
Content-Length: 11

Bad Request

[ferventcoder]

Ideas?

[ferventcoder]

Here is where you can test this - http://chocotest.apphb.com

[ferventcoder]

Trying to push a package up from the command line and I'm getting the issue of it losing my header (or something).

This was not occurring previously, and this was the only change I made, so I'm left to wonder if it is something happening when this module inspects the headers and makes changes.

[devatwork]

Was your code previously working on AppHarbor?

The documentation of the AppHarbor loadbalancer is quite limited. But it might be that your header is available under the key HTTP_X-NuGet-ApiKey. Could you confirm this.

[ferventcoder]

It was working, yes. I was testing locally but ran out of time for awhile. Coming back to it in a few

[ferventcoder]

So completely locally I cannot reproduce this. I am running your module locally...stepping through it and it is doing fine.

[ferventcoder]

After taking it out, the pushes are working again. So it's definitely something in here.

[ferventcoder]

But it's not necessarily with your code, just that it is possibly not doing something yet. It doesn't look like it is removing anything from what I saw.

[ferventcoder]

For what it's worth, your code would have replaced this: https://github.com/chocolatey/chocolatey.org/tree/master/chocolatey/Website/MvcOverrides

[ferventcoder]

I filed an issue with appharbor support - http://support.appharbor.com/discussions/problems/7148-custom-headers-are-changedlost

[devatwork]

The code in my module does not remove any headers. It only modifies HTTP_X_FORWARDED_FOR, HTTP_X_FORWARDED_PROTO and HTTP_X_REQUESTED_WITH.

However, it might be the case that one of the collection methods I use has a side effect. I will investigate.

[devatwork]

After some testing I was able to reproduce the problem consistently on the AppHarbor servers but not on my local machine for some reason.

I have been browsing the .NET framework code but I was not able to find the cause yet. Will keep looking.

[ajukraine]

I have experienced same problem. After removing "Premotion-AspNet-AppHarbor-Integration", NuGet started working properly.

Please check my repository with fully working solution - https://github.com/ajukraine/NugetServer.AppHarbor

[Tyst]

I was using this module briefly, until I ran into some issues using it with Pjax. AppHarbor advised me to add the following to my web.config:

<appSettings>
    <!-- AppHarbor Setting to stop AppHb load balancer internal port numbers from showing up in URLs-->
    <add key="aspnet:UseHostHeaderForRequestUrl" value="true" />
</appSettings>

I no-longer needed this module after that.

You can find more info about the setting here: http://msdn.microsoft.com/en-us/library/hh975440

Many thanks to the author, all the same :)

[ferventcoder]

Interesting solution. These app harbor guys. They need to write it all down somewhere. :)