Search the Community
Showing results for tags 'http'.
Currently ESET is rewriting body chunks and removing trailers with HTTP Transfer-Encoding:chunked. HTTP Server sends: HTTP/1.1 200 OK Trailer: Server-Trailer-C Content-Type: text/plain; charset=utf-8 Transfer-Encoding: chunked d Hello, World! D Hello, World! 0 Server-Trailer-C: XYZ With Web Protocols > Enable HTTP Protocol checking enabled, the client reads this response: HTTP/1.1 200 OK Trailer: Server-Trailer-C Content-Type: text/plain; charset=utf-8 Transfer-Encoding: chunked 1a Hello, World!Hello, World! 0 With HTTP Protocol checking disabled, it reads exact response as written by the Server. Excluding the server from being checked/handled in "URL Address management" did not work either. Web Protection should not rewrite the body nor remove the trailers, unless there is a good reason. If there is a good reason, there should be a way to disable it for a particular server, because currently the only way is to disable the HTTP Protocol checking completely. This behavior is making go compiler net/http tests fail when you have ESET installed. To reproduce the issue, here is a minimal standalone program: hxxp://egonelbre.com/support/eset/httptrailer.exe hxxp://egonelbre.com/support/eset/httptrailer.go (in case you do not want to run the binary directly) Probably related issue: