Hi
When I execute a post with an attachment, Load UI generates a boundary (I already removed the quotes) like this
Content-Type: multipart/form-data; boundary="----=_Part_63_784287734.1559741312548"
And the "Attachment part"
------=_Part_63_784287734.1559741312548
Content-Type: application/pdf
Content-Disposition: form-data; name="file"; filename="DPA Piece 1.pdf"
The access management of our application refuse (I think) some characters within the name of the boundary section:
I find in the logs
HTTP 403
[msg "Failed to parse request body."] [data "Multipart: Invalid boundary in C-T (characters)."] [severity "CRITICAL"] [ver "OWASP_CRS/3.0.0"]
When I execute from a web brower with a name = ------WebKitFormBoundaryCz9zYIwaDfkUV9bO, I don't have the issue.
Any idea how to change he name of the boundary?
Thanks
Solved! Go to Solution.
Hi @odesmaele,
You can modify the boundary value using the RequestFilter.filterRequest event handler, please see an example here: https://smartbear-cc.force.com/portal/KbArticleViewer?name=Troubleshooting-issues-with-adding-attach....
But, ReadyAPI is working according to the HTTP standards:
- https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
- https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html
So, it's better to check whether your server follows the standards.
Hi @odesmaele,
You can modify the boundary value using the RequestFilter.filterRequest event handler, please see an example here: https://smartbear-cc.force.com/portal/KbArticleViewer?name=Troubleshooting-issues-with-adding-attach....
But, ReadyAPI is working according to the HTTP standards:
- https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html
- https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html
So, it's better to check whether your server follows the standards.
I'll check with development team if standards are respected. Thanks for your answer
Hi all,
Thanks for your reply, @Nastya_Khovrina !
@odesmaele did you have a chance to check this? Is the question answered?
We are looking forward to hearing from you.