Andrew Hauck
Andrew Hauck
Is the example you provided here complete? We shouldn't be invoking `proxy_connect` unless `new_proxy` is called or `proxy` is set on `HttpPeer`. If I try your example code I see:...
Circling back to this it looks like there's an issue handling CONNECT responses. ``` [2024-04-13T14:47:12Z WARN pingora_core::protocols::http::v1::server] Respond header is already sent, cannot send again ```
What are you trying to accomplish? We have a [`BackgroundService`](https://github.com/cloudflare/pingora/blob/main/pingora-core/src/services/background.rs#L30) you can use to run background services and expose them to pingora.
> i need to initialize a redis client during startup, so it can be used on each request FYI as mentioned [here](https://github.com/cloudflare/pingora/blob/main/pingora-core/src/server/mod.rs#L264) if you start pingora with the daemonize flag...
> So, the solution is using Background Service I don't think so unless you need to query Redis out of band of making a request, on a fixed interval or...
What do debug level logs show?
I think the issue here is we don't set `end_of_stream` when the task is `HttpTask::Done`.
> I have a usecase, where the selected backend/upstream is dependent on the order of some values in a config file among other things. Do you mind expanding a bit...
This is a bug, we're not propagating upstream h2 trailers downstream, will have a patch for this soon.
We merged the fix internally last week it should sync this week.