You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why is this hardcoding 1.1? There are still severs that return 1.0, and when doing caching it's important to know whether it's a 1.0 or 1.1 type reply because that changes what you send back in to do validation.
The text was updated successfully, but these errors were encountered:
I assume this is because it wouldn't make sense for a server to respond with 1.0 when a 1.1 request was sent. But I don't have an RFC reference to back that claim up.
async-http-client/Sources/AsyncHTTPClient/HTTPHandler.swift
Line 656 in e2636a4
Why is this hardcoding 1.1? There are still severs that return 1.0, and when doing caching it's important to know whether it's a 1.0 or 1.1 type reply because that changes what you send back in to do validation.
The text was updated successfully, but these errors were encountered: