Bad Request (400) - The request could not be understood by the server due to malformed syntax

294 views
Skip to first unread message

jin.dh...@teknion.com

unread,
Dec 5, 2016, 11:44:25 AM12/5/16
to Fujitsu RunMyProcess Developer Community
Hello,

I have an button which continues the process. When I click on it I am getting this error mesage:

Bad Request (400) - The request could not be understood by the server due to malformed syntax

I looked at the PUT request body and it looks good as far as I can tell.

<feed
xmlns="http://www.w3.org/2005/Atom"
xmlns:p="http://www.runmyprocess.com/live/" xml:base="https://live.runmyprocess.com/">
<title>Process update request</title>
<link rel="self" href="live/111241403117814587/request/4d8f1782-bb06-11e6-bddf-0619bd984419/task/6/0"/>
<rights>(c) RunMyProcess</rights>
<category term="event" label="COMPLETE"/>
<entry>
<title>New parameters</title>
<id>0</id>
<category term="computed"/>
<content type="text/base64">eyJpZCI6IjIwMTYtMDA4MDEiLCAiZmlsZV9hdHRhY2htZW50IjpbXSwgInVzZXJfbmFtZSI6IkppbiBEaGFsaXdhbCIsICJwcm9jZXNzX3N0YXR1cyI6IkNsYXJpZmljYXRpb24gUmVxdWVzdGVkIiwgInJlcXVlc3RfaWQiOiI0ZDhmMTc4Mi1iYjA2LTExZTYtYmRkZi0wNjE5YmQ5ODQ0MTkiLCAiY3VzdG9tZXIiOiIxMTEyNDE0MDMxMTc4MTQ1ODciLCAiY3VycmVudF9kYXRlX2FuZF90aW1lIjoiMTItMDUtMjAxNiIsICJQX2Nvbm5lY3RlZF91c2VyIjp7ImxvZ2luIjoiamluLmRoYWxpd2FsQHRla25pb24uY29tIn0sICJyZXF1ZXN0X3R5cGUiOiJPdGhlciIsICJlbXBsb3llZV9uYW1lIjoiSmluIERoYWxpd2FsIiwgInByb2R1Y3RfZ3JvdXAiOiJhc2Rhc2Rhc2QiLCAicXVhbnRpdHkiOiIxMiIsICJjb250cmFjdCI6Im5vIiwgImR1ZV9kYXRlIjoiLSIsICJjcmVhdGVkX2J5IjoiSmluIERoYWxpd2FsIDEyLzUvMjAxNiAxMTozMTo0MyIsICJwcmljZV90eXBlIjoiVVBDSEFSR0UgJSIsICJwcmljZV90eXBlX2xpc3QiOiIyIiwgImRhdGUiOiIxMi81LzIwMTYgMTE6MzE6NDMiLCAiZGVzY3JpcHRpb25fb2ZfaXRlbXMiOiJhc2Rhc2QiLCAiZGF0ZV9jcmVhdGVkIjoiMTIvNS8yMDE2IiwgInJlcXVlc3Rfc2VudF90b19wcmljZXIiOiIxMi81LzIwMTYiLCAicmVxdWVzdF9wcmljZWQiOiIwIiwgImxhc3RfdmlzaXRlZCI6IjAiLCAiZGF5c19jcmVhdGlvbl90b19jaGVja2VkX291dCI6MCwgImRheXNfY3JlYXRpb25fdG9fcHJpY2VkIjpOYU4sICJjaG9pY2UiOiJ5ZXMiLCAicGNob2ljZSI6IiIsICJhY2tfY2hvaWNlIjoiIiwgImNzc19zb3VyY2UiOiI8c3R5bGU+XHJcclxyXHJccjwvc3R5bGU+IiwgIlBfbW9kZSI6IlRFU1QifQ==</content>
</entry>
</feed>

I need to know why this error is happening.
asdasd.png

jin.dh...@teknion.com

unread,
Dec 5, 2016, 3:26:28 PM12/5/16
to Fujitsu RunMyProcess Developer Community, jin.dh...@teknion.com

Pankaj Kumar

unread,
Dec 6, 2016, 4:34:11 AM12/6/16
to Fujitsu RunMyProcess Developer Community, jin.dh...@teknion.com
Hi Jin,

In your Put Request end point, request id is:- fed12072-bb1e-11e6-90dd-066d75fba2ef

And In Request payload:- 

 <link rel="self" href="live/111241403117814587/request/4d8f1782-bb06-11e6-bddf-0619bd984419/task/6/0"/>

Request ids are different (it should be same), and same request id is given in "base64" encoded content type node

"request_id":"4d8f1782-bb06-11e6-bddf-0619bd984419"

I am not able to reproduce this scenario, kindly share more details on it.

Thank you,
Pankaj Kumar
Fujitsu RunMyProcess Support

On Tue, Dec 6, 2016 at 1:56 AM, <jin.dh...@teknion.com> wrote:

--

teknion.com <http://www.teknion.com>

<https://www.facebook.com/Teknion> <https://twitter.com/teknion>
<https://www.pinterest.com/teknion/>
<https://www.linkedin.com/company/teknion> <https://instagram.com/teknion/>
<https://www.youtube.com/Teknion>
<https://itunes.apple.com/us/app/teknion-eshow-chicago/id529619476?mt=8>

Confidentiality Notice: This communication, including any attachments, may
contain information that is confidential and privileged. [It may constitute
non-public information and is intended to be conveyed only to the
designated recipient(s).] If the reader or recipient of this communication
is not the intended recipient, or you believe that you have received this
communication in error, please notify us immediately by return e-mail and
promptly delete this e-mail including any attachments without reading or
saving them in any manner. Any other distribution, copying or disclosure is
prohibited and may be unlawful. We accept no responsibility for changes
made to this e-mail or to any attachments after transmission from our
office.

--
Fujitsu - RunMyProcess
---
You received this message because you are subscribed to the Google Groups "Fujitsu RunMyProcess Developer Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supportforum+unsubscribe@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at https://groups.google.com/a/runmyprocess.com/group/supportforum/.
To view this discussion on the web visit https://groups.google.com/a/runmyprocess.com/d/msgid/supportforum/085e8765-9975-48c1-a831-444986e2b665%40runmyprocess.com.

jin.dh...@teknion.com

unread,
Dec 6, 2016, 10:04:15 AM12/6/16
to Fujitsu RunMyProcess Developer Community, jin.dh...@teknion.com
That was my mistake. I copied and pasted from two different requests I was testing.

This is the correct information from a single request:

URL:https://live.runmyprocess.com/live/111241403117814587/request/c9ee0e51-bbc2-11e6-b33e-066d75fba2ef/task/52/0
Request Method:PUT
Status Code:400 Bad Request
Remote Address:10.0.3.65:3128

<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:base="https://live.runmyprocess.com/">
<title>Bad Request (400) - The request could not be understood by the server due to malformed syntax</title>
<link rel="resource" href="live/111241403117814587/request/c9ee0e51-bbc2-11e6-b33e-066d75fba2ef" title="" />
<category term="error" />
<id>live/111241403117814587/request/c9ee0e51-bbc2-11e6-b33e-066d75fba2ef</id>
<rights>(c) RunMyProcess 2016</rights>
</feed>

I attached some images to better illustrate what is happening.

activity.png
error.png
process report.png
Screen.png
View.png

Pankaj Kumar

unread,
Dec 7, 2016, 6:29:55 AM12/7/16
to Fujitsu RunMyProcess Developer Community, jin.dh...@teknion.com
Hi Jin,

In your configuration, I am not able to find any specific that could relate to error 400. Kindly let me know your available time for screen sharing to troubleshoot the issue.

Thank you,
Pankaj Kumar
Fujitsu RunMyProcess Support

Reply all
Reply to author
Forward
0 new messages