The custom HTTP reverse proxy (molohttp) written in Swift is not performing as expected after replacing Caddy. The proxy was eventually reverted to Caddy. This ticket tracks the architectural investigation needed before attempting the swap again.
Steps to Reproduce
Not provided.
Expected Behaviour
molohttp should perform comparably to Caddy as an HTTP reverse proxy.
Actual Behaviour
"Molohttp is working but the performance is not what I expect."
"Async in Swift is more sensitive than Python. Need to investigate."
The proxy was reverted to Caddy with the note "we're on Caddy again."
Environment
Custom HTTP reverse proxy (molohttp) written in Swift
Previous proxy: Caddy
Web framework for admin/API has implicit dependencies (connection pooling, keep-alive, header rewriting) that break when the underlying HTTP server changes
Attempted to replace the web framework but the admin panel has deep dependencies on the framework that made it impossible to swap cleanly
Reported by retoor via DevPlace.
## Summary
The custom HTTP reverse proxy (molohttp) written in Swift is not performing as expected after replacing Caddy. The proxy was eventually reverted to Caddy. This ticket tracks the architectural investigation needed before attempting the swap again.
## Steps to Reproduce
Not provided.
## Expected Behaviour
molohttp should perform comparably to Caddy as an HTTP reverse proxy.
## Actual Behaviour
- "Molohttp is working but the performance is not what I expect."
- "Async in Swift is more sensitive than Python. Need to investigate."
- The proxy was reverted to Caddy with the note "we're on Caddy again."
## Environment
- Custom HTTP reverse proxy (molohttp) written in Swift
- Previous proxy: Caddy
- Web framework for admin/API has implicit dependencies (connection pooling, keep-alive, header rewriting) that break when the underlying HTTP server changes
- Attempted to replace the web framework but the admin panel has deep dependencies on the framework that made it impossible to swap cleanly
---
*Reported by **retoor** via DevPlace.*
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
The custom HTTP reverse proxy (molohttp) written in Swift is not performing as expected after replacing Caddy. The proxy was eventually reverted to Caddy. This ticket tracks the architectural investigation needed before attempting the swap again.
Steps to Reproduce
Not provided.
Expected Behaviour
molohttp should perform comparably to Caddy as an HTTP reverse proxy.
Actual Behaviour
Environment
Reported by retoor via DevPlace.