Luca Bruno

Ack, thanks for feedback. I'm thus closing this PR on `hyper` side. > I suppose if we think of redirects as a form of retry, then access to changing the...

For reference, this is the JS `fetch()` behavior from specs (point 12 of https://fetch.spec.whatwg.org/#http-redirect-fetch): ``` If one of the following is true status is 301 or 302 and request’s method...

> The multishot version of recvmsg I'm still confused about. I think parts of the msghdr are still relevant to the function even though the buffer it is designed to...

There is still one UX question open about how to expose this: https://github.com/tokio-rs/io-uring/blob/6785e666869993f81414a5cfad501ef714c742e9/io-uring-test/src/tests/net.rs#L1295-L1296 On the same topic, it is also relevant to note that multishot recvmsg also needs to have...

Sorry my availability is a bit spotty as I'm busy taking care of other stuff offline. No I don't have other things to merge before the next release.

I had a look at all the linked issues and also asked some feedback out of band; I sketched some code to implement this, and I want to recap the...

Closing as fixed in 3.9 by https://github.com/Kong/docker-kong/pull/724.

@AaronO from https://github.com/seanmonstar/httparse/pull/156#issuecomment-1980339794: > There is a minor cleanup bundled in this PR (marking several functions as pub(crate)) which I did in order to make sure I wasn't changing public...

Apologies, I should've added some breadcrumbs upfront; I've update the PR description with some refs now. I think this `rustc` builtin lint [description](https://doc.rust-lang.org/stable/nightly-rustc/rustc_lint/builtin/static.UNREACHABLE_PUB.html) describes it better than what I could...

@AaronO Ack, I'll split the `pub` cleanup as I was originally offering to. I've marked this PR as a draft, as I think we aren't going to land this as-is...