Martin Algesten
Martin Algesten
My first thought is that it sounds simple enough. However on second thought, we have what we can think of as a constant trickle ice. A candidate might not be...
Hi there! In a quick test, I don't find a problem with what you suggest, but it makes me a bit uneasy. In a patch versions of rustls between 0.23.19...
For now, I will not try to fix this. However I leave this bug open so that others can express an interest in the problem.
@SergioRibera thanks for the PR. As a side note, the rest of Rust API is deliberately using very simple types, i.e. `&str` instead of `T: AsRef` – I might change...
Closing since we are moving to 3.x
This is available in 3.1.4
Hi there! I don't think we get enough information to do anything here. Could you run ureq with `RUST_LOG=trace` and post the results?
The validation should probably be up to the transport chain. Some refactoring to make that happen.
This is somewhere between a bug and enhancement. The intention is to support the use case, but the current behavior isn't exactly broken since it's deliberate.
@rawler thanks for submitting this. I've been thinking back/forth on whether we can land it. In some respects it can be considered a breaking change.