Javier Sanchez Gil

## Update I have been researching what the best API response for `Expect` might be: The different proposals for what might be the best option are: 1. If we're talking...

## Update Finally, it has been decided to retain the current option that launches with the changes of `connection 3.0` and `uvicorn` among the proposed options, as it is a...

## Update I've been implementing the different responses of the API if the request contains the `Expect` header as we discussed with the rest of the team. Currently, it handles...

## Update The error that was arising with the `Expect` header was fixed, and several cases were tested: Without Expect header: ```console root@wazuh-master:/# curl -k -X GET "https://localhost:55000/?pretty=true" -H "Authorization:...

## Update The requested changes were added, it was decided to leave the encoding of values as they are for the moment, it's how we've been working with the rest...

## Update - I worked on the requested changes in the review by creating a `middleware` to handle the header. - I've been making changes to the code and testing...

## Update - I am still conducting tests on the errors mentioned earlier. - I managed to solve the error that was thrown when Content-Length exceeds the maximum allowed ```console...

## Update - A middleware was created to control the `Expect` header in API requests - The following checks were performed: *With `Expect` 100-continue* ```console root@wazuh-master:/# curl -k -X GET...

## Update - The requested syntax changes and modifications to the output of `expect_failed_error_handler` were added - Its functionality was checked again: ```console root@wazuh-master:/# curl -k -X GET "https://localhost:55000/?pretty=true" -H...

## Update - I was looking at how the tests are divided, how to develop it and getting started - I start to create the test_case script on the issue