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.

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

NTLM http response error , failure to read HTTPResponse is not handling malformed bluecoat http response special characters #118

Closed
ziyiwang opened this issue May 13, 2024 · 1 comment · Fixed by #120

Comments

@ziyiwang
Copy link

hi ,we have some NTLM responses coming back from our upstream bluecoat proxies

and the response is not accepted by alpaca , in this module
2024/03/22 15:34:14.930490 proxy-go:168: [] Got2 "malformed HTTP response """ response, retri ed with auth in proxy.go page full err object is null?

in transport.go

func (t *transport) RoundTrip(req *http.Request) (*http.Response, error) {

can we split this function
return http.ReadResponse(t.reader, req)

into separeate sendrequest , get response etc, so we can get the response back first before deciding its a malformed http response

@ziyiwang
Copy link
Author

i found the issue, its related to the extra httpresponse body bluecoat is sending back with ntlm auth challenge, i will submit a PR soon

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

Successfully merging a pull request may close this issue.

1 participant