[dotnet] Update dependency BenderProxy to 1.1.2 #14965
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.0.0
->1.1.2
Release Notes
jimevans/BenderProxy (BenderProxy)
v1.1.2
==================================
This release fixes two bugs in BenderProxy. The first bug is that if a socket
exception is encountered after shutdown of the proxy has been requested, the
proxy now swallows and ignores the exception. Since socket processing is
asynchronous, it's possible for the proxy to attempt connection after no
socket exists, and the exception is benign, since a shutdown was explicitly
requested anyway.
The second bug is in the processing of responses that utilize chunked
encoding. Previously, after reading the results of a chunk, the proxy tried
to read the length of the next chunk, by reading the next line of the body
stream. However, if there are no more chunks, this could cause the reader
to attempt reading past the end of the stream, causing an exception. To
mitigate this, after reading a chunk, the proxy now advances the stream
pointer two bytes, past the carriage-return/line-feed pair (CRLF) that
marks the end of a chunk. The proxy can then properly determine if it's
reached the end of the stream before attempting to read another chunk.
v1.1.1
==================================
This release changes the behavior of the proxy when multiple headers with the
same name are encountered. Previously, BenderProxy would concatenate the
values for multiple header instances with commas. However, parsing these
multiple values back out was nearly impossible, since the header value could
legitimately contain a comma. Now, the proxy concatenates the values using
carriage-return/line-feed pairs (CRLF), which the header value cannot
contain, because a CRLF pair signifies the end of a header in HTTP. This
enables the user to properly separate multiple header values when handling
HTTP traffic. Note that this is a proxy-only change; it does not affect
the actual HTTP traffic across the wire.
v1.1.0
==================================
This release adds support for persistent or so-called "keep-alive" connections
to be used. This allows BenderProxy to enable scenarios like authentication
using connection-based protocols like NTLM. The proxy now defaults to using
persistent connections. To revert to the previous behavior of closing the
connection to the server on every HTTP request, set the EnableKeepAlive
property of the HttpProxy to false.
Additionally, it attempts to make multiple subsequent calls that should reuse
the same socket more thread-safe, and keep them from stepping on one another.
Unfortunately, the way this is currently implemented is likely to introduce
a performance bottleneck in the proxy, because only one request can be
processed at a time. A rearchitecture to allow parallel HTTP calls should be
created at some point.
Finally, this release fixes a bug in parsing of HTTP headers. Header names,
according to spec are supposed to be case-insensitive, and the proxy was
not treating them that way.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.