On Tue, Nov 13, 2018, at 11:53 PM, Andreas Jaeger wrote:
> Reviewing a patch that changed http://eavesdrop.o.o to https, I checked
> and noticed that the URL gives a misconfiguration error. Should we stop
> running Apache on port 443 for eavesdrop - or configure the server
> properly with https?
>
Reviewing a patch that changed http://eavesdrop.o.o to https, I checked
and noticed that the URL gives a misconfiguration error. Should we stop
running Apache on port 443 for eavesdrop - or configure the server
properly with https?
Sending it here so that somebody can clean it up later and we
