Enhance middleware resilience and optimize HTTP/3 handling to use context_agent as mcp_server

[pledou]

This pull request updates the Nextcloud integration in the ex_app/lib/mcp_server.py file to patch the HTTP3 adapter..

Nextcloud Adapter and HTTP3 Handling

• Added a _patch_disable_http3 function that monkey-patches the Nextcloud session adapters (NcSessionApp and AsyncNcSessionApp) to always disable HTTP3, improving compatibility with certain server configurations. This patch is applied at import time.

[janepie]

Hey @pledou, can you please explain why you think these changes are necessary? Please also don't add unnecessary whitespaces, it makes the diff a bit unreadable.

[pledou]

My goal was to use OpenWebui to call context_agent as MCP tool. I had also to disable http3 because both nextcloud and OpenWebui are under Traefik reverse proxy with HTTP3 activated: It is a fast patch to make it work without retrograding the full stack in HTTP2. I did these changes weeks ago. I have to review the other change concerning NextcloudApp instead of AsyncNextcloudApp to add logs before-after and if necessary rollback this change

[pledou]

@janepie, apologies for the noises. I have double checked today that the change in UserAuthMiddleware could add robustness but is absolutely not necessary, so I have removed it in order to focus on the HTTP3 workaround.

[janepie]

Thanks for the cleanup!
I still don't really get why you think this is necessary, disabling HTTP3 in general is not something we want to do. Can you describe your issue with HTTP3 a bit in detail?