Do not set up Host header for CNAME #560
Open
+1
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue with Kerberos authentication in HTTP requests. Specifically, the issue occurred when the SPN (Service Principal Name) was being retrieved and the Host header in the HTTP request was being set to the final resolved host name from the URL.
This causes problems when working with proxies that must authenticate the client and then redirect clients. It is not clear why this was done in the original code. Without setting this header, everything starts working.
Example
service1.example.com-> proxy.example.com -> <target server>
In this case, the proxy service uses a single account with all SPNs for all services after it (e.g., HTTP/service1.example.com and HTTP/proxy.example.com). Therefore, everything works when the client retrieves any SPN. However, the Host header in the request was also changed, which caused the proxy to not understand which service to redirect the request to.