liamwhite
liamwhite
Regarding the need to explicitly add {sha, rsa}, it seems like we cannot express the following constraint as ssl opts: - Allow SHA1WithRSA for trusted root certificates in the chain...
Okay. Is that describing the behavior that will be implemented in OTP 28, or how it is supposed to work in OTP 27?
related: #93
@chrismccord as far as I can tell, EntryUploader is an internal API so there shouldn't be any compatibility issues. If there are compatibility issues I would actually expect them to...
It requires it to work at all. It will not work without the Phoenix PR because the Phoenix PR enables the most important part of it, the copyless socket sends....
@chrismccord I tested the Phoenix PR but could not find a way in which it broke backwards compatibility, since it continues to pass all external API tests. But I'm not...
I'm really sorry for the confusion. - The Phoenix PR is intended to be backwards compatible with other Phoenix scripts. I tested it, and it doesn't cause any issues on...
I wasn't aware they were exported/public API, so that's fair. I will close these out and let the devs decide on the best path forward to resolve the performance issue.
I assume the filesystem example is just to provide something easy for caddy developers to replicate, not for the sake of how caching would actually be used.
I am not sure I can make this interact correctly with the redirect step unless I reimplement the entire redirect step: ```elixir @spec get(url()) :: result() def get(url) do request(:get,...