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
@pedrorijo91 Thanks for laying out those problems. I agree that it would be nice to unify the design and the code a bit, and that it should be easy to get a download by name rather than auto-detecting. I doubt we'll ever have binary packages for Linux, though.
#145
Open
Michaelalmada opened this issue
Nov 30, 2023
· 0 comments
@pedrorijo91 Thanks for laying out those problems. I agree that it would be nice to unify the design and the code a bit, and that it should be easy to get a download by name rather than auto-detecting. I doubt we'll ever have binary packages for Linux, though.
I put in a page rule to override the aggressive caching for /download/win. I think in the long run that we should redesign the page so it can be cached (i.e., use javascript for auto-detection but have the various options clickable as a fallback).
(Somewhat orthogonal is that we should actually return correct cache-control headers from the app to cloudflare, and then we could use "normal" caching rules, and make caching rules at the app level. IIRC, I turned on the "cache everything" rules because there are a bunch of pages that could be cached but don't output the correct headers.
I put in a page rule to override the aggressive caching for
/download/win
. I think in the long run that we should redesign the page so it can be cached (i.e., use javascript for auto-detection but have the various options clickable as a fallback).(Somewhat orthogonal is that we should actually return correct cache-control headers from the app to cloudflare, and then we could use "normal" caching rules, and make caching rules at the app level. IIRC, I turned on the "cache everything" rules because there are a bunch of pages that could be cached but don't output the correct headers.
Originally posted by @peff in git/git-scm.com#1129 (comment)
The text was updated successfully, but these errors were encountered: