背景
當下restful接口程式設計風格流行,大家争相晉仿,筆者最近的開發架構自定義了校驗用戶端傳過來JSON的工具類。
在接收到用戶端json參數時可以校驗是否存在非法sql注入參數。
![](https://img.laitimes.com/img/_0nNw4CM6IyYiwiM6ICdiwiI0gTMx81dsQWZ4lmZf1GLlpXazVmcvwFciV2dsQXYtJ3bm9CX9s2RkBnVHFmb1clWvB3MaVnRtp1XlBXe0xCMy81dvRWYoNHLwEzX5xCMx8FesU2cfdGLwMzX0xiRGZkRGZ0Xy9GbvNGLpZTY1EmMZVDUSFTU4VFRR9Fd4VGdsYTMfVmepNHLrJXYtJXZ0F2dvwVZnFWbp1zczV2YvJHctM3cv1Ce-cmbw5CN2UTN4EmYhNzYwUGM4MmZyYzXyEzN0MTM3EzLchDMyIDMy8CXn9Gbi9CXzV2Zh1WavwVbvNmLvR3YxUjLyM3Lc9CX6MHc0RHaiojIsJye.png)
由于接口傳回400,前端沒處理,直接導緻前端無響應。
現在要對其進行改造,讓前端可以正常接獲得異常資訊。
解決方法
import org.springframework.core.Ordered;
import org.springframework.core.annotation.Order;
import org.springframework.http.HttpHeaders;
import org.springframework.http.HttpStatus;
import org.springframework.http.ResponseEntity;
import org.springframework.http.converter.HttpMessageNotReadableException;
import org.springframework.web.bind.annotation.ControllerAdvice;
import org.springframework.web.context.request.WebRequest;
import org.springframework.web.servlet.mvc.method.annotation.ResponseEntityExceptionHandler;
import static com.h2.mes.common.RestfulResponseMessage.SYSTEM_ERROR;
@Order(Ordered.HIGHEST_PRECEDENCE)
@ControllerAdvice
public class RestExceptionHandler extends ResponseEntityExceptionHandler {
@Override
protected ResponseEntity<Object> handleHttpMessageNotReadable(HttpMessageNotReadableException ex, HttpHeaders headers, HttpStatus status, WebRequest request) {
final String errorMessage = ex.getMessage();
final String[] msgs = errorMessage.split(";");
return ResponseEntity.ok(RestfulResponseMessage.errorResult(SYSTEM_ERROR,msgs[0]));
}
}
RestfulResponseMessage.errorResult(SYSTEM_ERROR,msgs[0])
是封裝的自定義異常資訊方法
改善後效果
參考資料:https://www.toptal.com/java/spring-boot-rest-api-error-handling