-
Notifications
You must be signed in to change notification settings - Fork 50
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
HTTP error (can't write to /deployments/file-uploads) when not setting content-type #634
Comments
Yeah without the content-type then the message body is null
The stacktrace is no longer, but platform-http-vertx seems to not want to read the message body because there is no content-type header. We may want to relax this so it works like other camel http components. |
It is CURL that uses this content-type when you don't specify it. Content-Type -> application/x-www-form-urlencoded And since the data is not a key=value (not form data) then the body is null |
So it is because platform-http have file-uploads enabled out of the box, which webhook should disable. |
Its a general problem for camel-k with platform-http-vertx where vertx would store form-data to disk. I cant see a desire to want this in camel-k style integrations where uploads would be stored to a temp folder. |
I created a JIRA ticket in camel core project |
@lburgazzoli yeah its a 1 year old bug, any comments? |
yeah, I think this bug was meant to be addressed by camel or camel-quarkus, I think we can close ti |
Ok tracked by that CAMEL ticket |
I've just added a webhook-source Kamelet in apache/camel-kamelets#14.
When bound with the following binding:
I've noticed that if I call it with:
... then everything goes fine. But without the content-type:
Then it fails because it probably tries to store some temp data in an illegal location.
Maybe the content is interpreted as a binary file and there's some caching mechanism in place. Maybe we should use a writable dir for that.
The text was updated successfully, but these errors were encountered: