http status 400 bad request

背景:

http 请求,路径参数没有进行urlEncoded,出现报错。

错误表现:

错误日志:

复制代码
 The valid characters are defined in RFC 7230 and RFC 3986
        at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:482)
        at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:263)
        at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63)
        at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:926)
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791)
        at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52)
        at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
        at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        at java.lang.Thread.run(Thread.java:750)

URL 解析策略不同

Resin

  • 对URL字符的检查相对宽松

  • 默认允许更多特殊字符

  • 更注重兼容性而非严格遵循RFC规范

Tomcat

  • 严格遵循RFC 7230和RFC 3986规范

  • 对特殊字符有严格限制

  • 更注重安全性和标准符合性

|{}\[\]"\都属于特殊字符串

源码

HTTP 请求行解析入口
org.apache.coyote.http11.Http11InputBuffer#parseRequestLine()

复制代码
org.apache.coyote.http11.Http11InputBuffer

if (this.parsingRequestLineQPos != -1 && !this.httpParser.isQueryRelaxed(this.chr)) {
	this.request.protocol().setString("HTTP/1.1");
	invalidRequestTarget = this.parseInvalid(this.parsingRequestLineStart, this.byteBuffer);
	throw new IllegalArgumentException(sm.getString("iib.invalidRequestTarget", new Object[]{invalidRequestTarget}));
}

if (this.httpParser.isNotRequestTargetRelaxed(this.chr)) {
	this.request.protocol().setString("HTTP/1.1");
	invalidRequestTarget = this.parseInvalid(this.parsingRequestLineStart, this.byteBuffer);
	throw new IllegalArgumentException(sm.getString("iib.invalidRequestTarget", new Object[]{invalidRequestTarget}));
}


package org.apache.tomcat.util.http.parser;
public class HttpParser {

	private final boolean[] IS_ABSOLUTEPATH_RELAXED = new boolean[128];
	private final boolean[] IS_QUERY_RELAXED = new boolean[128];

	public HttpParser(String relaxedPathChars, String relaxedQueryChars) {
	for(int i = 0; i < 128; ++i) {
		if (IS_CONTROL[i] || i == 32 || i == 34 || i == 35 || i == 60 || i == 62 || i == 92 || i == 94 || i == 96 || i == 123 || i == 124 || i == 125) {
			this.IS_NOT_REQUEST_TARGET[i] = true;
		}

		if (IS_USERINFO[i] || i == 64 || i == 47) {
			this.IS_ABSOLUTEPATH_RELAXED[i] = true;
		}

		if (this.IS_ABSOLUTEPATH_RELAXED[i] || i == 63) {
			this.IS_QUERY_RELAXED[i] = true;
		}
	}

	this.relax(this.IS_ABSOLUTEPATH_RELAXED, relaxedPathChars);
	this.relax(this.IS_QUERY_RELAXED, relaxedQueryChars);
}

}

public boolean isQueryRelaxed(int c) {
	try {
		return this.IS_QUERY_RELAXED[c];
	} catch (ArrayIndexOutOfBoundsException var3) {
		return false;
	}
}

先把 0-127 号 ASCII 字符全部扫一遍

  • IS_NOT_REQUEST_TARGET[i] = true → 表示该字节默认禁止出现在路径/查询串

  • 禁止列表 = RFC 3986 保留字符之外 的所有符号:
    " # < > \ ^ ````` { | } 以及空格、控制字符

    也就是说,只要不在这个黑名单里,就默认放行 ;反之必须被 relaxedPathChars/relaxedQueryChars 显式加白。

| 十进制 | 字符 | 默认是否被禁 | 备注 |
|-------|-------|--------|--------------|---|
| 32 | 空格 | ✅ | 必须 URLEncode |
| 34 | " | ✅ | 双引号 |
| 35 | # | ✅ | 片段标识符 |
| 60 62 | < > | ✅ | XML/HTML 危险 |
| 63 | ? | ❌ | 查询分隔符,放行 |
| 92 | \ | ✅ | 反斜杠 |
| 94 | ^ | ✅ | 脱字符 |
| 96 | ````` | ✅ | 反引号 |
| 123 | { | ✅ | 左花括号 | |
| 124 | ` | ✅ | 竖线(管道符 |
| 125 | } | ✅ | 右花括号 |

tomcat兼容

复制代码
@Slf4j
@Configuration
public class TomcatConfig implements WebServerFactoryCustomizer<TomcatServletWebServerFactory> {

    /**
     * RFC 3986 之外、Tomcat 默认拦截的常见字符
     * 空格、#、<>、^、`、{}、|、\、[]、"
     */
    private static final String RELAXED_CHARS = " #<>^`{}|[]\\\"";
    
    @Override
    public void customize(TomcatServletWebServerFactory factory) {
        factory.addConnectorCustomizers(connector -> {
            connector.setProperty("relaxedQueryChars", RELAXED_CHARS);
            connector.setProperty("relaxedPathChars", RELAXED_CHARS);
            log.info(">>>> Tomcat relaxed characters: {}", RELAXED_CHARS);
        });
    }
}
相关推荐
Goodbye3 天前
大模型无状态架构:从 HTTP 协议到 Harness AI 工程的深度解析
http
霜落长河9 天前
抛弃TCP改用UDP,HTTP3怎么了?
http
之歆10 天前
现代 HTTP 客户端深度解析:Fetch 与 Axios
chrome·网络协议·http
程序员mine10 天前
HTTPS-TLS加密与证书完全指南(下)
网络协议·http·https
SomeOtherTime10 天前
http协议处理播放video/mp4视频
http
llz_11211 天前
web-第五次课后作业
前端·后端·http
曾阿伦11 天前
netcat / ncat / socat 用法详解与示例
linux·http·信息与通信
cyforkk11 天前
破除网络协议迷雾:TCP、TLS 与 HTTP 的“连环套”逻辑
网络协议·tcp/ip·http
VidDown11 天前
视频协议传输全解析:从 HTTP/HTTPS 到 HLS/DASH 的完整旅程
javascript·网络·http·https·编辑器·音视频·视频编解码
Patrick_Wilson12 天前
Cookie 作用域避坑:父域泄漏、同名优先级与多环境隔离
前端·http·浏览器