News for hackers. Stuff that matters.
Re:Caddy 0.9 Released with All New Core by dvdplm on Tuesday July 19, 2016 @03:50AM (#12120435)
Can Caddy work as a reverse proxy to other backend services? And if so, can I use QUIC for the backend and plain TCP for the front-end? Would that give me any benefit?
Re:Caddy 0.9 Released with All New Core by aexaey on Tuesday July 19, 2016 @04:43AM (#12120604)
- Can Caddy work as a reverse proxy to other backend services?

Yes. Use this in your Caddyfile:

  proxy /api 10.20.30.40:8080 
- And if so, can I use QUIC for the backend

No, QUIC is not supported at the moment: https://caddyserver.com/blog/implementing-http2-isnt-trivial

- and plain TCP for the front-end?

Yes, if you mean HTTP/1.x. Also, you can serve static files from the proxy itself. Everything not mentioned in explicit "proxy" directive would be served from local files in the same directory as Caddifile.

Re:Caddy 0.9 Released with All New Core by aexaey on Tuesday July 19, 2016 @06:55AM (#12120987)
Re:Caddy 0.9 Released with All New Core by mholt on Tuesday July 19, 2016 @09:30AM (#12121594)
> can I use QUIC for the backend and plain TCP for the front-end? Would that give me any benefit?

Caddy only has a QUIC server implementation. But I'm inclined to think that if you have a QUIC->TCP flow going on, you will lose most of the benefits of QUIC at the TCP part.