Straight forward. Use the proxy as a sort of "git-based API gateway" which can handle rate limiting of excessive traffic. Busy clients get a helpful backoff message and upstream SCM servers are not impacted by repeated pushes from errant or careless clients.
While I'm not sure of the Jetty machinery around this area, it seems perfectly doable. It's also a minor feature that finos/git-proxy had. It was very aggressive (some amount of pushes per minute or per hour - I can't remember).
Straight forward. Use the proxy as a sort of "git-based API gateway" which can handle rate limiting of excessive traffic. Busy clients get a helpful backoff message and upstream SCM servers are not impacted by repeated pushes from errant or careless clients.
While I'm not sure of the Jetty machinery around this area, it seems perfectly doable. It's also a minor feature that finos/git-proxy had. It was very aggressive (some amount of pushes per minute or per hour - I can't remember).