Enrico Zimuel

@matyhtf very cool! Let me know if I can help in any way. Thanks!

@matyhtf any news on the proposal of using stream? Thanks!

@gabbydgab The `getParsedBody()` works only with GET/POST for `application/x-www-form-urlencoded`. XHTML 1.x forms only support GET and POST. That said, you can also use PUT with `x-www-form` but you need to...

@Nyholm can you review this PR? Thanks.

@Nyholm I see your point. I did the change throwing an `InvalidArgumentException` if the user or the password is not URL encoded.

@Nyholm I checked [rfc3986](https://www.rfc-editor.org/rfc/rfc3986#page-18) and the correct regex is as follows: ``` ^(?:[a-zA-Z0-9_\-\.~!\$&\'\(\)\*\+,;=:]|%[A-Fa-f0-9]{2})+$ ``` We need to check for valid `% HEXDIG HEXDIG` that's why I used `%[A-Fa-f0-9]{2}`. I provided...

@Nyholm I was thinking that we should throw two different exceptions for the user and for the password. Can we add specific Exception classes extending `\InvalidArgumentException`?

@GinoPane you mentioned that the issue is a `trailing slash` in your setting. Can you write an example to reproduce the issue? Thanks!

Thanks @GinoPane. I confirm that the issue comes when you add a `trailing slash` in your host URL. Interesting the issue happens only for some endpoints, like `indices.create`. Do you...

Don't worry, I'll provide the fix. Thanks for the report!