CJK in URL causes error in webserver about helidon HOT 3 CLOSED

I've reproduced this. The webserver immediately closes the connect upon hitting the exception which results in an empty response to the client. This is clearly a bug. On an error the server should be returning the correct HTTP status (maybe 400 in this case? See next point).

The next question is if the URL is valid as represented in the HTTP request sent to the server. It appears as though curl is not encoding the URL. The webserver is assuming that incoming URLs are correctly encoded (as defined by the HTTP protocol). In this case the URL in the HTTP request is not URL encoded (It is not http://localhost:8080/greet/%E5%B0%8F%E9%AB%98). And therefore the webserver gets the exception.

If you try the same thing but use a browser to enter the URL it should work, because the browser encodes the URL. It worked for me with both Chrome and Firefox.

But we do need to fix the error handling in the webserver so that it handles the exception and returns an HTTP status code.

from helidon.

@barchetta I've targeted this to 1.0

from helidon.

This is fixed by PR #796

from helidon.