Will Norris

Thanks for the good reproduction case. This is definitely an issue in the [gifresize](https://github.com/willnorris/gifresize) library, so I'll move this issue there. Simple reproduction steps there: ``` sh go run ./example...

Possibly related to willnorris/imageproxy#61 and #1

I don't have any plan to implement this myself, so can't really give an ETA. Someone that is sufficiently interested would need to do the work. However, I'm honestly not...

Hey @striker2000, thanks for this patch! Sorry it's taken a couple of week to get back to you. I think this is certainly a good approach; my only reservation is...

the resize icon for the 'x' is kind of clever. But I'm not sure that I get the relevance of the nesting dolls... ?

Similar to my comment on #286, if you're trying to prevent abuse, why isn't the solution request signatures? Sure we could prevent requests larger than 10000x10000, but that still doesn't...

I'll take a closer look at thing later, but my initial thought is that we should probably expose this through a "minCacheDuration" flag using [flag.Duration](https://golang.org/pkg/flag/#Duration). Then, we only use that...

Can you speak more about the motivation behind this change? Originally, imageproxy didn't scale up at all, since you could always just scale an image in CSS. The `scaleUp` option...

I'm not opposed to supporting the format, but I imagine it will run into the same problem as webp and HEIC (some of which is discussed in #114 and #292),...

Yeah, I'm totally supportive of adding that. I suspect the performance hit would be negligible, and we might be able to come up with some clever shortcuts to keep the...