Spring MVC optionally returning no view in a single mapping

Question

I have a case where i need to :

Return a 304 not modified status if the blog hasnt been modified
Or return the blog view if it's been modified since If-Modified-Since request header

The problem is when i want to return 304 status, how do i tell spring mvc not to assume another view from the null return, and start sending the response with the status immediately ?

@RequestMapping(value={"/blogs/{blogId}"}, method=RequestMethod.GET)
public String hello(final HttpServletRequest req, final HttpServletResponse resp, final Model model,
        @PathVariable("blogId") final String blogId) {
    if (isModified(req, blogId)) {
        resp.setStatus(HttpServletResponse.SC_NOT_MODIFIED);
        return null; // this doesnt stop spring mvc to assume a view name
    }

    populate(model, grabBlog(blogId));
    return "blog";
}

Markus Malkusch · Accepted Answer · 2014-01-12T12:32:02.467

From the HTTP perspective returning a view doesn't make sense at all. The Spring documentation covers that use case:

@RequestMapping
public String myHandleMethod(WebRequest webRequest, Model model) {

    long lastModified = // 1. application-specific calculation

    if (request.checkNotModified(lastModified)) {
        // 2. shortcut exit - no further processing necessary
        return null;
    }

    // 3. or otherwise further request processing, actually preparing content
    model.addAttribute(...);
    return "myViewName";
}

There are two key elements to note: calling request.checkNotModified(lastModified) and returning null. The former sets the response status to 304 before it returns true. The latter, in combination with the former, causes Spring MVC to do no further processing of the request.

My bad for not being clear. But What i want is not returning view, but set the status and flush the response immediately. I was assuming that spring mvc returns a view even if i return a null value. It turns out that my error was caused by something else, so my assumption was wrong. Thanks so much for sharing this, i was reinventing the wheel by manually returning 304. — Bertie, Jan 12 '14 at 14:27

score -2 · Answer 2 · answered Jan 12 '14 at 12:12

You can create an exception with the appropriate annotation and then throw it. Spring will then generate a page for that error code.

From: http://spring.io/blog/2013/11/01/exception-handling-in-spring-mvc

@ResponseStatus(value=HttpStatus.NOT_FOUND, reason="No such Order")  // 404
public class OrderNotFoundException extends RuntimeException {
    // ...
}

Spring MVC optionally returning no view in a single mapping

2 Answers2