> On Dec 26, 2019, at 11:09 AM, hymie! <hy...@lactose.homelinux.net> wrote: > > In my case, the backend is not running Apache. It's running software that > I didn't write, in a language I don't know (ruby), using a custom port, > and it's doing its own port-listening and request-responding. The > underlying software doesn't even support HTTPS, let alone HSTS, and I'm > trying to get Pound to wrap HTTPS around it.
If you can’t figure out how to make the backend set the desired header, you could put another proxy (e.g. apache or nginx) in front of it that speaks HTTP and knows how to set headers. I don’t believe pound can do this. > I'm about 85% of the way there, which is probably good enough, but it feels > like HSTS (if I can turn it on) might be the missing key. HSTS is a good thing -T -- pound mailing list pound@apsis.ch https://admin.hostpoint.ch/mailman/listinfo/pound_apsis.ch
