Will Norris

Looks like [decoding progressive jpegs is supported](https://github.com/golang/go/commit/8b624f607f726347dc48a1ec4989deb868890105), but no mention of encoding.

And [this post from Nigel](https://groups.google.com/forum/#!topic/golang-nuts/6HZKs4YCnmM) doesn't sound encouraging. > Nothing is planned. > > IIRC, if you want to tackle this yourself, note that there are two > dimensions (S...

To be clear, I don't think this needs to be closed. I think it's a fine feature request, it's just one that we likely wouldn't be able to add for...

I'm certainly open to the idea in theory. Some time ago, I tried doing the same thing for my own website... combining imageproxy and other similar go services into a...

Are you hoping to use imageproxy as a drop-in replacement of the existing proxy? Same path, same query parameters, etc? Just trying to better understand what additional options would be...

The other thing you could do is to provide a thin layer that accepts request using whatever API you want (pulling options off query params, potentially even with different parameter...

Do you know if the proxy is passing along the IF-X headers to the origin server? If so, it's possible that it's receiving a 304 response from there, not actually...

okay, gotcha... I think I misunderstood. So it looks to be fetching the image bytes from the remote server on first load and caching the unmodified image, it's just the...

okay, definitely a bug :) But unfortunately I don't have any bright ideas off the top of my head... you'll likely just need to trace the request a bit more...

was this a remote URL that wasn't setting its own cache headers?