Adjust boundary test cases for the less strict parsing

This commit is contained in:
Victor Hora
2018-11-14 16:06:43 -05:00
committed by Felipe Zimmerle
parent b638e523af
commit cbf2fe9703
2 changed files with 5 additions and 5 deletions

View File

@@ -1618,7 +1618,7 @@
{
"enabled":1,
"version_min":300000,
"title":"multipart parser (boundary special char - trailing comma+token)",
"title":"multipart parser (boundary special char - trailing exclamation+token)",
"client":{
"ip":"200.249.12.31",
"port":123
@@ -1633,7 +1633,7 @@
"User-Agent":"curl/7.38.0",
"Accept":"*/*",
"Content-Length":"330",
"Content-Type":"multipart/form-data;boundary=0000,1111",
"Content-Type":"multipart/form-data;boundary=0000!1111",
"Expect":"100-continue"
},
"uri":"/",
@@ -1850,7 +1850,7 @@
},
"expected":{
"http_code": 403,
"debug_log": "boundary was quoted.*No boundaries found in payload"
"debug_log": "Invalid boundary in C-T \\(characters\\).*boundary was quoted."
},
"rules":[
"SecRuleEngine On",
@@ -1911,7 +1911,7 @@
},
"expected":{
"http_code": 403,
"debug_log": "boundary was quoted.*No boundaries found in payload"
"debug_log": "Invalid boundary in C-T \\(characters\\).*boundary was quoted."
},
"rules":[
"SecRuleEngine On",