Question
Cisco Systems
IN
Last activity: 27 Sep 2017 12:24 EDT
Mapping of Incoming Response from a Connect-REST failed
We are trying a consume a REST Service through connect-REST, Whenever we are sending a huge payload in the Request, we are getting the below response and error:
Response:
---------
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>414 Request-URI Too Large</title> </head><body> <h1>Request-URI Too Large</h1> <p>The requested URL's length exceeds the capacity limit for this server.
</p> </body></html>
Error:
---------
** Error mapping incoming response to <.ResponsePropertyName>: org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
We are trying a consume a REST Service through connect-REST, Whenever we are sending a huge payload in the Request, we are getting the below response and error:
Response:
---------
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>414 Request-URI Too Large</title> </head><body> <h1>Request-URI Too Large</h1> <p>The requested URL's length exceeds the capacity limit for this server.
</p> </body></html>
Error:
---------
** Error mapping incoming response to <.ResponsePropertyName>: org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
at [Source: java.io.StringReader@2f7857d5; line: 1, column: 2]
However when the Request payload is small, The incoming response is rightly mapped and we can find the same on Clipboard.
We found the following solution on PDN and this didn't seem to work:
https://pdn.pega.com/support-articles/exception-thrown-incoming-response-connect-rest
The following error was seen even after implementing the work-around mentioned in the link:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>414 Request-URI Too Large</title> </head><body> <h1>Request-URI Too Large</h1> <p>The requested URL's length exceeds the capacity limit for this server.
</p> </body></html>
JPMorgan Chase & Company
US
Hi,
Under Apache, the limit is a configurable value, LimitRequestLine. Change this value to something larger than its default of 8190 if you want to support a longer request URI. The value is in /etc/apache2/apache2.conf. If not, add a new line (LimitRequestLine 10000) under AccessFileName .htaccess.
However, note that if you're actually running into this limit, you are probably abusing GET to begin with. You should use POST to transmit this sort of data -- especially since you even concede that you're using it to update values. If you check the link above, you'll notice that Apache even says "Under normal conditions, the value should not be changed from the default."
Pegasystems Inc.
IN
Hi Rakshitha,
need to check for large json mapping from our end. Please attach response json which is causing the error and what is the prpc version you are using?
Pegasystems Inc.
US
A similar discussion is happening here:
https://collaborate.pega.com/discussion/not-able-create-tables-using-pvs-setup-data-model
Have you attempted to send the data as the POST body rather than in the URL itself? Many APIs allow/expect this.
Cisco Systems
IN
Hi pylaa,
I don't have a response for the failure case mentioned in the post because the request is being stopped at the apache web-layer. the request isn't hitting the web-service.