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

Error processing HTTP/2 request #850

Closed
nkartyshov opened this Issue Oct 19, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@nkartyshov
Member

nkartyshov commented Oct 19, 2016

Lines from the log file:

17:13:08.319 [pool-3-thread-1840] DEBUG com.adguard.filter.proxy.a - TCP id=109173 Cannot read HTTP request Http host is empty for request PRI * HTTP/2.0
17:13:08.321 [Thread-548] DEBUG com.adguard.commons.b.s - TCP id=109173 address=/127.0.0.1:41713 Read 30 bytes from socket channel
17:13:08.321 [pool-3-thread-1840] DEBUG com.adguard.filter.proxy.ssl.q - TCP id=109173 Server alert raised. Level: warning, Description: close_notify close_notify(0)

Full log file: adguard.txt

@nkartyshov nkartyshov added the Bug label Oct 19, 2016

@ameshkov ameshkov changed the title from Error to parsing http request to protocol http/2.0 to Error processing HTTP/2 request Oct 19, 2016

@ameshkov ameshkov added this to the 2.8 milestone Oct 19, 2016

@ameshkov

This comment has been minimized.

Show comment
Hide comment
@ameshkov

ameshkov Oct 19, 2016

Member

@nkartyshov in order to fix this you should do the following:

  1. Change Protocol enum, rename Http into Http1
  2. Change isHttpProtocol method so that it was detecting only HTTP/1.X
Member

ameshkov commented Oct 19, 2016

@nkartyshov in order to fix this you should do the following:

  1. Change Protocol enum, rename Http into Http1
  2. Change isHttpProtocol method so that it was detecting only HTTP/1.X
@nkartyshov

This comment has been minimized.

Show comment
Hide comment
@nkartyshov

nkartyshov Oct 21, 2016

Member

fixed

Member

nkartyshov commented Oct 21, 2016

fixed

@nkartyshov nkartyshov closed this Oct 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment