Unable to receive POST data for Content-Type: application/x-www-form-urlencoded

Question

Unable to receive POST data for Content-Type: application/x-www-form-urlencoded

Closed this issue 7 years ago · 11 comments

I send the POST sample is fine for any Content-Type except "application/x-www-form-urlencoded".

send:
curl -X POST localhost:19092/topics/foo/messages?sync -H 'Content-Type:text/plain' -d 'blah blah blah'

Response:
{
"partition": 0,
"offset": 41
}

send:
curl -X POST localhost:19092/topics/foo/messages?sync -H 'Content-Type:application/x-www-form-urlencoded' -d 'blah blah blah'

Response:
{
"error": "Message size does not match Content-Length: expected=14, actual=0"
}

How do i receive POST for Content-Type is application/x-www-form-urlencoded?

Answer 1 · 2017-03-08T08:30:32.000Z

@cizexzza at the moment only text/plain with utf-8 encoding is supported. Why do you need application/x-www-form-urlencoded if text/plain works fine for you?

Answer 2 · 2017-03-08T08:52:13.000Z

oh, I can not change the data source and the data Content-Type is application/x-www-form-urlencoded .

Answer 3 · 2017-03-08T09:00:19.000Z

@cizexzza why you cannot change the content-type? How do you make requests? I mean what programming language+framework are you using?

Answer 4 · 2017-03-08T09:07:05.000Z

i can change my programming language requests content-type , but i can not change data from other machine equipment , the equipment send data Content-Type is application/x-www-form-urlencoded.

Answer 5 · 2017-03-08T18:46:53.000Z

@cizexzza I am just curious what "other machine equipment" you are using that it does not let you these change?

Answer 6 · 2017-03-09T01:40:08.000Z

ya. i just can collect it data.

Answer 7 · 2017-03-09T05:40:03.000Z

@cizexzza sorry, I do not understand you.

Answer 8 · 2017-03-15T06:00:21.000Z

@cizexzza still interested in this? I can add support for application/x-www-form-urlencode.

Answer 9 · 2017-05-28T06:47:55.000Z

@horkhe I would be more than happy to add this .

Answer 10 · 2017-05-31T23:53:21.000Z

@asitm9 if you want to do that yourself, then please be my guest. By the way, we at Mailgun do not rely on HTTP interface anymore, we use gRPC internally and in fact recommend everybody to do the same.

Answer 11 · 2017-06-17T00:38:04.000Z

@cizexzza it will become available in v0.13.1, but you can build Kafka-Pixy from sources right now. It should work like this:

curl -X POST localhost:19092/topics/foo/messages?sync -H 'Content-Type:application/x-www-form-urlencoded' -F 'msg=blah blah blah'