Using HttpServletResponse in Java Web: Captcha Generation, Response Header Control, and URL Path Best Practices

The article begins with a common use case of HttpServletResponse —creating a captcha image. It shows how to create a BufferedImage , draw random numbers with Graphics2D , set the content type to image/jpeg , and prevent caching by setting the expires , Cache-Control , and Pragma headers before writing the image to the response output stream.

Next, it demonstrates setting various response headers to control browser behavior:

Disabling caching with response.setDateHeader("expries", -1) , response.setHeader("Cache-Control", "no-cache") , and response.setHeader("Pragma", "no-cache") .

Refreshing the page every 5 seconds using response.setHeader("refresh", "5") .

Performing a redirect with response.sendRedirect("/JavaWeb_HttpServletResponse_Study_20140615/index.jsp") , which internally sets a 302 status and a Location header.

The article then discusses URL path conventions in a web project. It recommends using a leading slash ( / ) for absolute paths and explains that when the slash is interpreted by the server it refers to the web application root, while when used by the browser it points to the webapps directory. Examples include using ServletContext.getRealPath("/download/1.JPG") , server‑side forwards, and JSP include directives.

For client‑side navigation, the article shows how to replace hard‑coded project names with the dynamic context path:

response.sendRedirect(request.getContextPath()+"/index.jsp");

and JSP/HTML links such as:

<a href="${pageContext.request.contextPath}/index.jsp">Home</a>

It also provides a comprehensive example that combines JSP directives, script and stylesheet inclusion using the context path, a form submission, and a hyperlink, illustrating the consistent use of the absolute path pattern.

Finally, the article clarifies the difference between response.getOutputStream() (for binary data) and response.getWriter() (for text data), noting that they are mutually exclusive and that the servlet container will close the stream automatically after the service method completes.