forum

Home / DeveloperSection / Forums / Why spring MVC optionally returning no view in a single mapping

Ask Question

Why spring MVC optionally returning no view in a single mapping

Anonymous User 2485 02-Feb-2015

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";
}

asp.net asp.net mvc 
Updated on 02-Feb-2015
Anonymous User

Anonymous User

Follow
I am a content writter !

Can you answer this question?

Answer

1 Answers

Anonymous User

Anonymous User

02-Feb-2015

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";
}

 

Liked By