Problem with nginx handling the actual path of images

Question

In the project, the uploaded files were renamed by sha1. After a picture was uploaded, it was named c2e47454e951697811c0531949d4d318. The access path on the browser side is: /img/c2e47454e951697811c0531949d4d318. Note that there is no picture suffix! After I deployed...

仅有的幸福 · Answer

First of all, since you have already sha1'd it, you don't need to store its suffix. When storing, change everything to the sha1 value

Then, if you directly access Nginx to get the image, you will not get the correct file name, and some other logic is not easy to handle, so just write a controller to handle it:

    @RequestMapping(value = "imgs/{sha1}/download", method = RequestMethod.GET)
    @ResponseBody
    public HttpEntity downloadAttachment(@PathVariable("sha1") String sha1)
            throws UnsupportedEncodingException {
        Attachment attachment = attachmentService.getBySha1(sha1);

        if (attachment == null) {
            throw new ResourceNotFoundException();
        }

        HttpHeaders header = new HttpHeaders();
        header.setContentType(MediaType.APPLICATION_OCTET_STREAM);
        String filename = new String(attachment.getName().getBytes("GB2312"), "ISO_8859_1");
        header.setContentDispositionFormData("attachment", filename);
        header.add("X-Accel-Redirect", String.format("/img/c2/e4/%s", sha1));
        header.add("X-Accel-Charset", "utf-8");

        return new HttpEntity(null, header);
    }

In this way, you can not only use Nginx’s cache, but also use your own code to do some logical operations, and you can also add the function of permission judgment

In addition, Nginx configuration does not need to be changed