Skip to content
This repository has been archived by the owner on Apr 26, 2023. It is now read-only.

DotNet: forward all headers to client response #134

Merged

Conversation

afili
Copy link
Member

@afili afili commented Jul 15, 2014

added logic to forward all headers that are allowed from the server response to the client response.

proposed fix for #67

@afili afili changed the title forward all headers to client response DotNet: forward all headers to client response Jul 15, 2014
bsvensson added a commit that referenced this pull request Jul 25, 2014
…sponse

DotNet: forward all headers to client response
@bsvensson bsvensson merged commit c4baa30 into Esri:master Jul 25, 2014
@bsvensson bsvensson added this to the 1.1 milestone Aug 12, 2015
@pfoppe
Copy link
Contributor

pfoppe commented Jun 15, 2016

As a result of this... duplicate header values are being passed back to the client. We are operating in a 'Integrated Windows Authentication' environment and I can see both the server and persistent-auth headers are duplicated. Was this intentional and do we see any potential impacts with this scenario? I did not see any application functionality degraded, but did not look right. Thanks!

@bsvensson
Copy link
Member

@pfoppe - You're correct. The proxy needs to be smarter about header values, some should be passed through, some should not. For example Server should not be passed on and duplicated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants