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

broker doesn't respond if not able to read all of the incoming payload #2761

Closed
kzangeli opened this issue Dec 12, 2016 · 1 comment
Closed
Labels
Milestone

Comments

@kzangeli
Copy link
Member

kzangeli commented Dec 12, 2016

In a functest where we needed to check error for TOO BIG payload size, we got the problem that the broker is unable to respond with a 'nice error' when this occurs.

To provoke the problem, we simply lie to the broker, saying that the incoming payload is bigger than it really is:

payload='{ "id": "E1", "type": "T1" }'
orionCurl --url /v2/entities --payload "$payload" -H "Content-Length: 6000000"

In connectionTreat, an attempt to send a decent response is done, but due to a limitation in libmicrohttpd, the response isn't sent.

A question to be sent to the mailing list of MHD.

@fgalan
Copy link
Member

fgalan commented Dec 19, 2016

Fixed by PR #2774

@fgalan fgalan closed this as completed Dec 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants