Forum Discussion
richie
Community Hero
Hey shadab1312,
That xmlprolog error's like a catch all xml parser error....really not helpful when trying to diagnose what went wrong.
I suspect that the base64 encode value is larger than what is accepted by the defaults in readyapi.
The way to prove this would be if you submit your request with a base64 encoded value that is a lot smaller than what you tried. I appreciate your endpoint might be expecting a certain length value so youll probably get a 400 or 422 or some other client error if you submitted a base64 value a lot smaller than what you need, but try it.....this will prove if the issue is because the base64 encode value is too large.
Might help if you can you post your headers on the request and response please?
Im on my phone at the moment, but i remember theres a setting in the preferences for chunking/payload size. Id tweak those settings to try and fix this if i were you.
Nice one,
Rich
That xmlprolog error's like a catch all xml parser error....really not helpful when trying to diagnose what went wrong.
I suspect that the base64 encode value is larger than what is accepted by the defaults in readyapi.
The way to prove this would be if you submit your request with a base64 encoded value that is a lot smaller than what you tried. I appreciate your endpoint might be expecting a certain length value so youll probably get a 400 or 422 or some other client error if you submitted a base64 value a lot smaller than what you need, but try it.....this will prove if the issue is because the base64 encode value is too large.
Might help if you can you post your headers on the request and response please?
Im on my phone at the moment, but i remember theres a setting in the preferences for chunking/payload size. Id tweak those settings to try and fix this if i were you.
Nice one,
Rich
shadab1312
4 years agoNew Contributor
I tried another thing:
I used the request content as parameter and checked Post QueryString option(See screenshot).
Now it works!!!
- richie4 years agoCommunity Hero
holdit - you had a very large base64 encoded value in a tag and then you posted it as a query parm instead?
Surprised that worked with the length of the base64 value - it looked like it was close to the URL char limit - but it from what you've explained, it sounds like your endpoint would only allow types of multiform-urlencoded rather than application/xml to begin with....
glad you sorted!
Rich
Related Content
- 4 years ago
- 6 years ago
- 9 years ago
Recent Discussions
- 22 days ago