Fair enough, http is enough - I anyways have one caddy to rule them all. However, if your app is picky about reverse proxying, e.g. headers, please add a sample caddy config. It's often the first thing I'm looking for if I'm trying out a tool and want to host it under a subdirectory before configuring a subdomain.

▲

sam_lowry_ 2 days ago | parent [-]

No, HTTP is not enough, I submitted a couple HTTP-only links to HN lately, they got flagged within half an hour, even HN crowd can not open HTTP links anymore ;-)

▲

smashed a day ago | parent [-]

That's not really HN's fault but all modern browsers will warn the user before accessing an http site with a security warning.

My point was not to use http only as a finished solution, but to let the admin front the http-only service with their TLS termination solution of choice.

	▲	sam_lowry_ a day ago \| parent \| next [-]
		We are talking about hobbyists here.
	▲	dsvf 9 hours ago \| parent \| prev [-]
		... Of which (TLS terminators) caddy is IMO the easiest for hobbyists, as was the starting point of this subthread