Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: HTTP post transform bad request #2917

Closed
vitalijs1 opened this issue May 11, 2023 · 5 comments
Closed

[Bug]: HTTP post transform bad request #2917

vitalijs1 opened this issue May 11, 2023 · 5 comments

Comments

@vitalijs1
Copy link

Apache Hop version?

2.4.0

Java version?

java.version=11.0.10

Operating system

Windows

What happened?

there is one HTTP post transform that works fine in hop 2.1.0
but in version 2.4.0 it throws an error 500 "Internal Server error"

checked that Request entity field for api URL is the same in both versions

test hop pipeline attached:
getSessionId.zip

Issue Priority

Priority: 1

Issue Component

Component: Actions, Component: API, Component: Hop Run, Component: Transforms

@sramazzina
Copy link
Contributor

Hi @vitalijs1
not clear to me if your example is a fully working example. I noticed that in your SOAP request there are username and password fields. Remember that we need a working example that we can use to reproduce the problem and take a look at your issue

@sramazzina sramazzina changed the title [Bug]: HTTP post transformation [Bug]: HTTP post transform bad request May 12, 2023
@sramazzina sramazzina added P3 Nice to have and removed P1 Critical Issue labels Jul 5, 2023
@KBoersch
Copy link

I can confirm the problem. Until 2.2 I can send a POST request with HTTP POST. After that, until now (2.5) I can't. If I use the Rest Client transform instead, I'm able to send my POST request again.

I'm sending the request to a report-server, that expects the following json body:

{"submit":"submit",
"reportname":"Reportname",
"gitlab_branch":"MASTER",
"jobname":"2023-07-12-10-25"}

content-type json, that's it.

The body and content-type remains the same in rest client transform.

@hansva
Copy link
Contributor

hansva commented Jul 12, 2023

.take-issue

@hansva
Copy link
Contributor

hansva commented Jul 12, 2023

This was probably caused by enabling multipart on the data transfers, I changed this into an option this should resemble the old way of posting the requests more. It would be great if you could test this and provide feedback

@KBoersch
Copy link

Yeah sure. I will give you feedback, as soon as the new snapshot is out :)

@hansva hansva closed this as completed in 112d1dc Jul 12, 2023
hansva added a commit that referenced this issue Jul 12, 2023
add option to enable/disable multipart data requests, fixes #2917
@hansva hansva added this to the 2.6 milestone Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants