Will Norris

Wow, this is a phenomenally detailed bug report! Thanks, that super useful. What you're doing is basically what I would have done if I ever got around to adding size...

can you provide an example of this happening?

Hmm, that's a really interesting idea. I'm pretty behind on merging some existing PRs that *might (?)* interact with this a little (like #237). So it will almost certainly take...

Given the existing baseURL support, this seems to be of somewhat limited value at the cost of additional complexity. So no, probably not something is out in core right now....

reopening issue, as I have some ideas for how to implement aliases without too much complexity.

Is the original image a 2:3 ratio? If so, then that shouldn't be a problem. If it's not, then you're right that it's not possible. imageproxy never distorts or skew...

My first guess would be that the origin server is not providing any caching headers, and indeed that looks to be the case: ``` % curl -I -A "" "http://ids.si.edu/ids/deliveryService?id=CHSDM-1C3F9215FDF82-000001"...

Also, that's really cool to see that @creativecommons is using imageproxy! Are you able/willing to share more about how you're using it? (Just for my own curiosity)

Hey @BrianGreenhill, I'm finally catching up on outstanding PRs 😕 I'm curious what you think of the alternate approach in #235. Rather than wrapping the handler and limiting **all** requests...

interesting... I'm not sure why I've never paid attention to that before. You're definitely right that it's double caching the unmodified image, and we should fix that. I don't think...