Alexey Zapparov

I believe #776 and #783 are. Also, I just noticed a PR that I wanted to merge 4 years ago and never get to it, that I believe we should...

Alternative - I can cherry pick retriable and headers caching and cut 5.3.0 release instead.

Will merge #773

Oh, I have confused it with #754 indeed

After looking through the changes, I think it's fine to release 5.3.0 off the master by only excluding 1ba37c2, the rest looks fine for minor version bump. Doing that now

Released v5.3.0; Closing this ticket, as I agree we should add as many breaking changes as we can to avoid making major bumps a habbit ;D

Here's the list of backported commits: https://github.com/httprb/http/compare/v5.2.0...v5.3.0

@corymhall the problem is that I need to define some sort of DMZ where peers of the same SG can talk to each other freely, and additionally allow ingress from...

Probably, the problem that I'm having in `Pulumi.yaml`: ``` yaml options: refresh: always ```

Frankly, `pulumi refresh` on aws-native is really weird - constantly lots of warnings :((