Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: hyperium/hyper
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.14.15
Choose a base ref
...
head repository: hyperium/hyper
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.14.16
Choose a head ref
  • 8 commits
  • 17 files changed
  • 4 contributors

Commits on Nov 18, 2021

  1. feat(server): add HTTP/1 header read timeout option (#2675)

    Adds `Server::http1_header_read_timeout(Duration)`. Setting a duration will determine how long a client has to finish sending all the request headers before trigger a timeout test. This can help reduce resource usage when bad actors open connections without sending full requests.
    
    Closes #2457
    paolobarbolini authored Nov 18, 2021
    Configuration menu
    Copy the full SHA
    842c655 View commit details
    Browse the repository at this point in the history

Commits on Nov 24, 2021

  1. Configuration menu
    Copy the full SHA
    1010614 View commit details
    Browse the repository at this point in the history

Commits on Nov 29, 2021

  1. fix(http1): return 414 when URI contains more than 65534 characters (#…

    …2706)
    
    Previous behavior returned a 404 Bad Request. Conforms to HTTP 1.1 RFC.
    
    Closes #2701
    rajing authored Nov 29, 2021
    Configuration menu
    Copy the full SHA
    5f938ff View commit details
    Browse the repository at this point in the history

Commits on Nov 30, 2021

  1. fix(server): use case-insensitive comparison for Expect: 100-continue (

    …#2709)
    
    According to rfc2616#section-14.20 the header value is case-insensitive. Certain clients send the expectation as `100-Continue` and this should be handled by the server.
    
    Closes #2708
    JonathanMurray authored Nov 30, 2021
    Configuration menu
    Copy the full SHA
    7435cc3 View commit details
    Browse the repository at this point in the history
  2. 1 Configuration menu
    Copy the full SHA
    ce82425 View commit details
    Browse the repository at this point in the history

Commits on Dec 6, 2021

  1. fix(http2): received Body::size_hint() now return 0 if implicitly e…

    …mpty (#2715)
    
    An HTTP/2 stream may include a set of headers, and a flag signalling
    END-STREAM, even if a `content-length` isn't included. hyper wouldn't
    notice, and so the `Body` would report a size-hint of `0..MAX`. hyper
    now notices that the stream is ended, and couldn't possibly include any
    bytes for the body, and thus will give a size-hint of `0` exactly.
    seanmonstar authored Dec 6, 2021
    Configuration menu
    Copy the full SHA
    84b78b6 View commit details
    Browse the repository at this point in the history

Commits on Dec 9, 2021

  1. feat(http2): add http2_max_send_buf_size option to client and server

    This value is like a high-water mark. It applies per stream. Once a
    stream has buffered that amount of bytes to send, it won't poll more
    data from the `HttpBody` until the stream has been able to flush under
    it.
    seanmonstar committed Dec 9, 2021
    Configuration menu
    Copy the full SHA
    bff977b View commit details
    Browse the repository at this point in the history
  2. v0.14.16

    seanmonstar committed Dec 9, 2021
    Configuration menu
    Copy the full SHA
    41dee4a View commit details
    Browse the repository at this point in the history
Loading