Dear all,
I had the same problem (HTTP 414 Request Too Large) when using the ServiceParaEdit.jsp for changing a service parameter using Axis 1.5.1 and changed the method from GET to POST, but as a consequence, when changing a parameter, the aar was corrupted. Unfortunately, I did not further investigate the cause of this. Regards, Sven -----Original message----- From: VANEKEM, Olivier <[email protected]> Sent: Wed 07/07/10 18:40:45 To: [email protected]; Subject: [Axis2] Axis 2 Admin Console generates HTTP 414 Request Too Large We are using Axis 2 and the Admin console to edit some application specific parameters. However we found out that when the console is located behind a reverse proxy server such as Apache HTTP server, we receive a HTTP 414 Request Too Large error when trying to modify the parameters. This is due to the following : Our Web service uses WSDL2Java generated classes (including the skeleton) and the console shows a generated parameter called wsdl4jDefinition which is very large (up to 12000 characters for one of our services). When clicking on the button Change in the console Edit parameters form, the actual HTML form method is a GET. This means that all attributes on the form will end on the URL and passed by to the axis2-admin/editServicepara servlet. This is also not good from a security point of view since all parameters will appear appended to the browser url. The correct solution is to change the GET into a POST. Attached is the ServiceParaEdit.jsp that contains this patch. Rgds Olivier ---------- Olivier VANEKEM SAGA Consulting SA/NV Chief Operating Officer Atlas Park, Weiveldlaan 41, box 35, 1930 Zaventem, Belgium In March... SAGA goes open... Phone: +32 (0)2 714 94 95 Fax: +32 (0)2 714 90 99 Mobile: +32 (0)477 75 44 85 email: [email protected] linked in: http://www.linkedin.com/in/ovanekem internet: http://open.saga.be
