Open stsefanenko opened 6 years ago
your HTTP request body seems to not be in the right encoding, the body as you show looks like to have invalid characters and is not x-www-form-urlencoded
Yes, string is not urlencoded. True to say, may be it's ok to have such exception, but for me will be better to have some warning may be. And response code is 500 for such case which looks strange. May be will better to return 400 Bad Request?
can you check which part of vertx or netty takes this decision to send a 500 error ?
there is already some specific handling of errors : https://github.com/eclipse/vert.x/blob/master/src/main/java/io/vertx/core/http/impl/Http1xServerConnection.java#L497
in this case indeed we are sending a 400 errors
On 6 Sep 2018, at 15:39, stsefanenko notifications@github.com wrote:
Yes, string is not urlencoded. True to say, may be it's ok to have such exception, but for me will be better to have some warning may be. And response code is 500 for such case which looks strange. May be will better to return 400 Bad Request?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/eclipse/vert.x/issues/2616#issuecomment-419096901, or mute the thread https://github.com/notifications/unsubscribe-auth/AANxiopkDnmxvz0kqUe5SMT8_yTFmrjNks5uYSWcgaJpZM4WcwlV.
Looks like more netty bug, but I report here for investigation. I have a simple configuration like:
For special requests the code fails before my handler. Request like:
Error:
Vertx version: 3.5.0