Skip to content

Conversation

gbaz
Copy link
Contributor

@gbaz gbaz commented Mar 18, 2018

Resolves #659

The approach here is different than in that ticket. We just check if there is a "?real=true" at the end of the .tar.gz url. If there isn't, we bump the download count and redirect to a url that does have the path. If there is, then we just return the .tar.gz.

That way the cdn can cache the real url, and everything works as is.

@gbaz
Copy link
Contributor Author

gbaz commented Mar 18, 2018

This breaks some tests, they'll need to be fixed.

@hvr
Copy link
Member

hvr commented Mar 18, 2018

Let's hold off on this one for a bit to get us more time to consider the consequences for Hackage clients out there...

@gbaz
Copy link
Contributor Author

gbaz commented Mar 19, 2018

Indeed, we're blocked on at least changes to the hackage-security backends, and perhaps other tools as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

2 participants