dstufft/fenrir

Issues

• Comparison with other solutions?

  #55 opened 10 years ago by webmaven
  3

• RFC 7231 Section 6.6.6 - Handle Unknown HTTP Major versions

  #32 opened 11 years ago by dstufft
  2

• RFC 7230 Section 3.5 - Handle alternate line endings

  #15 opened 11 years ago by dstufft
  0

• RFC 7230 Section 3.5 - Handle extraneous prefaced CRLF

  #14 opened 11 years ago by dstufft
  0

• RFC 7230 Section 3.5 - Handle receiving what appears to be a HTTP response

  #17 opened 11 years ago by dstufft
  0

• RFC 7320 Section 3.2.4 - Handling of leading or trailing whitespace in a header field value

  #9 opened 11 years ago by dstufft
  0

• RFC 7320 Section 3.2.4 - Rejection of whitespace in field name

  #8 opened 11 years ago by dstufft
  0

• RFC 7230 Section 3.1.1 - Handle an improperly encoded URL

  #5 opened 11 years ago by dstufft
  0

• RFC 7320 Section 3.3.2 - Handle Multiple Content-Lengths

  #13 opened 11 years ago by dstufft
  2

• RFC 7320 Section 3.2.2 - Handling of multiple instances of the same header

  #7 opened 11 years ago by dstufft
  0

• RFC 7230 Section 3.2 - Header field names are case insensitive

  #6 opened 11 years ago by dstufft
  0

• RFC 7239 - Implement Forward Header

  #36 opened 11 years ago by dstufft
  0

• RFC 7230 Section 5.7.1 - Implement the Via header

  #19 opened 11 years ago by dstufft
  1

• 7233 - Implement Range Requests

  #35 opened 11 years ago by dstufft
  0

• RFC 7231 Section 7.4.2 - Implement Server response header

  #34 opened 11 years ago by dstufft
  0

• RFC 7231 Section 7.1.1.2 - Ensure that all responses have a Date header

  #33 opened 11 years ago by dstufft
  0

• RFC 7231 Section 5.1.1 - Expects

  #29 opened 11 years ago by dstufft
  1

• RFC 7230 Section 2.5 - Implement Limits

  #2 opened 11 years ago by dstufft
  4

• RFC 7231 Section 6.5.10 - If there is no Content-Length use a specific error response

  #31 opened 11 years ago by dstufft
  0

• RFC 7230 Section 6.5 - Flow Control and Connection Timeouts

  #22 opened 11 years ago by dstufft
  1

• RFC 7231 Section 6.3.5 - 204 No Content

  #30 opened 11 years ago by dstufft
  0

• RFC 7231 Section 4.3.8 - Determine handling of TRACE method

  #28 opened 11 years ago by dstufft
  1

• RFC 7231 Section 4.3.6 - Correctly handle CONNECT responses

  #27 opened 11 years ago by dstufft
  0

• RFC 7231 Section 4.3.2 - Prevent sending a message body in a HEAD response

  #26 opened 11 years ago by dstufft
  0

• RFC 7230 Section 9.4 - Preventing response splitting

  #25 opened 11 years ago by dstufft
  0

• RFC 7230 - Section 6.7 - Upgrade requests

  #24 opened 11 years ago by dstufft
  0

• RFC 7230 Section 6.6 - Graceful tear down of connections

  #23 opened 11 years ago by dstufft
  0

• RFC 7230 Section 6.4 - Limit number of concurrent TCP connections

  #21 opened 11 years ago by dstufft
  0

• RFC 7230 Section 6.3.2 - Parallel processing of pipelined requests

  #20 opened 11 years ago by dstufft
  0

• RFC 7230 Section 5.1 - Ensure URL Fragments are Ignored

  #18 opened 11 years ago by dstufft
  0

• RFC 7230 Section 3.3.1 - Implement Transfer Encoding

  #12 opened 11 years ago by dstufft
  2

• RFC 7230 Section 3.5 - Handle whitespace variations in request-line and status-line

  #16 opened 11 years ago by dstufft
  0

• RFC 7230 Section 3.3 - Handle zero length bodies

  #11 opened 11 years ago by dstufft
  0

• RFC 7230 Section 3.2.4 - Handling of obs-fold

  #10 opened 11 years ago by dstufft
  0

• RFC 7230 Section 3 - Safe handling of whitespace

  #4 opened 11 years ago by dstufft
  0

• RFC 7230 Section 2.6 - HTTP Version in a Response

  #3 opened 11 years ago by dstufft
  1