HTTP status code 200 (cache) vs status code 304?

[kazoostudios]

Can Glide serve images that are more aggressively browser cached - status 200 (cache) instead of 304?

[kazoostudios]

http://stackoverflow.com/questions/1665082/http-status-code-200-cache-vs-status-code-304

[reinink]

Originally Glide returned a 200 status code. Now it returns 200 for the first request, and 304 for subsequent requests. This was actually at request. See #20. I did a bunch of research into it at the time, and it seemed that returning a 304 was the correct way to do this.

I'm probably going to setup an option to define this however you want. However, in the meantime you're welcome to modify the response object manually. As per the docs, you can get the response object instead of simply outputting the image right away. Something like this:

$response = $server->getImageResponse();
// modify...
$response->send();

[reinink]

An update on this:

The next iteration of Glide will have a ResponseFactory interface, which will allow you to override the default response that is created to whatever you prefer. More details on that here.

I'm going to close this issue since we have it covered in that other issue. However, you can expect this feature in an upcoming release.