Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
带水的鱼儿
spring-framework
提交
6c684190
S
spring-framework
项目概览
带水的鱼儿
/
spring-framework
与 Fork 源项目一致
从无法访问的项目Fork
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
S
spring-framework
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
6c684190
编写于
7月 27, 2021
作者:
R
Rossen Stoyanchev
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Polishing contribution
Closes gh-27216
上级
a747cc3e
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
17 addition
and
23 deletion
+17
-23
spring-web/src/main/java/org/springframework/http/codec/multipart/SynchronossPartHttpMessageReader.java
...ttp/codec/multipart/SynchronossPartHttpMessageReader.java
+1
-1
spring-web/src/test/java/org/springframework/http/codec/multipart/SynchronossPartHttpMessageReaderTests.java
...odec/multipart/SynchronossPartHttpMessageReaderTests.java
+16
-22
未找到文件。
spring-web/src/main/java/org/springframework/http/codec/multipart/SynchronossPartHttpMessageReader.java
浏览文件 @
6c684190
...
...
@@ -356,7 +356,7 @@ public class SynchronossPartHttpMessageReader extends LoggingCodecSupport implem
this
.
isFilePart
=
(
MultipartUtils
.
getFileName
(
headers
)
!=
null
);
this
.
partSize
=
0
;
if
(
maxParts
>
0
&&
index
>
maxParts
)
{
throw
new
DecodingException
(
"Too many parts
("
+
index
+
"/"
+
maxParts
+
" allowed)"
);
throw
new
DecodingException
(
"Too many parts
: Part["
+
index
+
"] but maxParts="
+
maxParts
);
}
return
this
.
storageFactory
.
newStreamStorageForPartBody
(
headers
,
index
);
}
...
...
spring-web/src/test/java/org/springframework/http/codec/multipart/SynchronossPartHttpMessageReaderTests.java
浏览文件 @
6c684190
/*
* Copyright 2002-202
0
the original author or authors.
* Copyright 2002-202
1
the original author or authors.
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
...
...
@@ -165,37 +165,31 @@ public class SynchronossPartHttpMessageReaderTests extends AbstractLeakCheckingT
@Test
void
readTooManyParts
()
{
testMultipartExceptions
(
reader
->
reader
.
setMaxParts
(
1
),
ex
->
{
assertThat
(
ex
)
.
isInstanceOf
(
DecodingException
.
class
)
.
hasMessageStartingWith
(
"Failure while parsing part[2]"
);
assertThat
(
ex
.
getCause
())
.
hasMessage
(
"Too many parts (2/1 allowed)"
);
}
testMultipartExceptions
(
reader
->
reader
.
setMaxParts
(
1
),
ex
->
assertThat
(
ex
)
.
isInstanceOf
(
DecodingException
.
class
)
.
hasMessageStartingWith
(
"Failure while parsing part[2]"
)
.
hasRootCauseMessage
(
"Too many parts: Part[2] but maxParts=1"
)
);
}
@Test
void
readFilePartTooBig
()
{
testMultipartExceptions
(
reader
->
reader
.
setMaxDiskUsagePerPart
(
5
),
ex
->
{
assertThat
(
ex
)
.
isInstanceOf
(
DecodingException
.
class
)
.
hasMessageStartingWith
(
"Failure while parsing part[1]"
);
assertThat
(
ex
.
getCause
())
.
hasMessage
(
"Part[1] exceeded the disk usage limit of 5 bytes"
);
}
testMultipartExceptions
(
reader
->
reader
.
setMaxDiskUsagePerPart
(
5
),
ex
->
assertThat
(
ex
)
.
isInstanceOf
(
DecodingException
.
class
)
.
hasMessageStartingWith
(
"Failure while parsing part[1]"
)
.
hasRootCauseMessage
(
"Part[1] exceeded the disk usage limit of 5 bytes"
)
);
}
@Test
void
readPartHeadersTooBig
()
{
testMultipartExceptions
(
reader
->
reader
.
setMaxInMemorySize
(
1
),
ex
->
{
assertThat
(
ex
)
.
isInstanceOf
(
DecodingException
.
class
)
.
hasMessageStartingWith
(
"Failure while parsing part[1]"
);
assertThat
(
ex
.
getCause
())
.
hasMessage
(
"Part[1] exceeded the in-memory limit of 1 bytes"
);
}
testMultipartExceptions
(
reader
->
reader
.
setMaxInMemorySize
(
1
),
ex
->
assertThat
(
ex
)
.
isInstanceOf
(
DecodingException
.
class
)
.
hasMessageStartingWith
(
"Failure while parsing part[1]"
)
.
hasRootCauseMessage
(
"Part[1] exceeded the in-memory limit of 1 bytes"
)
);
}
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录