Why request params is always NULL for PUT method in tomcat deployed in heroku

Question

Whereas it is working fine for POST and DELETE methods. The same war is working for all HTTP methods in local installed tomcat. As checked with heroku docs, there is no configuration is related to this issue.

If it is due to parseBodyMethods, then we can have no control over tomcat config. We can make changes only in our war file.

Used tomcat version : Tomcat 8

score 0 · Answer 1 · answered May 17 '20 at 03:55

0

Your http contentType is xmlurlencoded?

answered May 17 '20 at 03:55

user6093307

11
1

HTTP Content-Type header is application/x-www-form-urlencoded – Mohamed Rafic S May 17 '20 at 05:44
tomcat may decode http post body when it's contentType is form-urlencoded and method is POST, see https://tomcat.apache.org/tomcat-8.0-doc/config/http.html – user6093307 May 17 '20 at 09:50
You could change the params parseBodyMethods – user6093307 May 17 '20 at 09:51
Yes we can. But it is possible if we have control over server.xml. In heroku deployment we can deploy a war file but there is no control over tomcat configuration. – Mohamed Rafic S May 17 '20 at 13:01

Why request params is always NULL for PUT method in tomcat deployed in heroku

1 Answers1