dgrr/http2

Issues

• WARNING: DATA RACE

  #69 opened 6 months ago by zishang520
  1

• Do you support h2c?

  #43 opened 3 years ago by ts-kst
  3

• broken integration with fasthttp

  #67 opened a year ago by pablolagos
  2

• fasthttp http2 Whether connection-level health probes are supported

  #66 opened a year ago by zxpdmw
  13

• WINDOW_UPDATE must be ignored on closed connection as stated by RFC 7540

  #64 opened 2 years ago by pemarko
  0

• DATA RACE

  #59 opened 3 years ago by balcieren
  6

• OMG! it's panic

  #58 opened 3 years ago by beaquant
  5

• panic: send on closed channel

  #55 opened 3 years ago by meehow
  2

• how to enable http2

  #61 opened 2 years ago by KazumiLine
  0

• Dispatch RequestCtx in it's own coroutine

  #53 opened 3 years ago by dgrr
  1

• ERROR: writeLoop: use of closed network connections when using firefox

  #60 opened 3 years ago by hiqsociety
  0

• When HTTP/2 client works with Client

  #54 opened 3 years ago by farss
  1

• Cancel a request

  #51 opened 3 years ago by dgrr
  0

• Does this http2 support proxy?

  #39 opened 3 years ago by liandeliang
  1

• More benchmarks and more tests

  #13 opened 3 years ago by dgrr
  1

• GoAway doesn't close the connection afterwards.

  #52 opened 3 years ago by dgrr
  0

• ReadTimeout timer not resetting?

  #27 opened 3 years ago by GitRowin
  16

• How to get rid of the channels while being thread-safe?

  #26 opened 3 years ago by dgrr
  1

• Streaming would be nice.

  #5 opened 3 years ago by dgrr
  2

• HTTP/2 Server Push

  #37 opened 3 years ago by efectn
  1

• Framing layer (with priorization, weight and dependency)

  #4 opened 3 years ago by dgrr
  2

• Check the input stream is even or odd, manage protocol errors, etc...

  #10 opened 3 years ago by dgrr
  1

• how do you have any domain names and not pre-specify the domain name?

  #30 opened 3 years ago by hiqsociety
  1

• Support PUSH_PROMISE?

  #7 opened 3 years ago by dgrr
  5

• Client doesn't support multiple connections.

  #25 opened 3 years ago by dgrr
  0

• Limit MAX_CONCURRENT_STREAMS and keep track of the streams opened

  #2 opened 3 years ago by dgrr
  0

• There's no way to upgrade WebSocket over HTTP/2 (on my implementation, of course)

  #22 opened 3 years ago by dgrr
  1

• Does not work using net.Listener with TLS

  #24 opened 3 years ago by gitfury
  13

• out of range

  #23 opened 3 years ago by dgrr
  0

• Fix stream states (or at least finish it)

  #3 opened 3 years ago by dgrr
  0

• Flow control

  #1 opened 3 years ago by dgrr
  0

• Client transport undefined

  #20 opened 3 years ago by trinhdaiphuc
  2

• Make settings frame great again

  #11 opened 3 years ago by dgrr
  0

• Support to HTTP/2 through raw TCP (no TLS)

  #8 opened 4 years ago by dgrr
  1

• Go modules support

  #17 opened 4 years ago by AMekss
  2

• HPACK is not working correctly and I have no idea

  #19 opened 4 years ago by dgrr
  1

• Header compression might be better

  #9 opened 4 years ago by dgrr
  1

• Post with empty data hangs

  #15 opened 4 years ago by AMekss
  4

• Do a Client

  #6 opened 4 years ago by dgrr
  1

• Working example with automatic https2 with letsencrypt using autocert will be nice.

  #14 opened 4 years ago by hiqsociety
  0

• Faster/better padding methods

  #12 opened 4 years ago by dgrr
  0