-
|
Hi, http: TLS handshake error from This happens if requesting software does not support TLS1.2 or 1.3 or accessing my site using IP directly (not with domain name). This is all attackers, scanners and bots. Not my clients. So far I do not use any logger middleware (except for debugging). Thus I use the default logger established after echo instance was created. It logs to regular log (stdout) and I inspect it with journalctl (I run as a systemd daemon). How can I stop it from logging messages beginning with http: TLS handshake error from? But keep the rest? |
Beta Was this translation helpful? Give feedback.
Answered by
aldas
Jul 19, 2021
Replies: 1 comment 4 replies
-
|
I think those messages are logged by http server logger. You could try to set log.SetOutput(ioutil.Discard)This is how you can set func main() {
e := echo.New()
s := http.Server{
Addr: ":8082",
Handler: e,
ErrorLog: nil, // set here logger to no-op logger
}
if err := s.ListenAndServe(); err != http.ErrServerClosed {
log.Fatal(err)
}
}and here is example for autoTLS with http.Server https://echo.labstack.com/cookbook/auto-tls/#server check |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Thanks aldas, but what you suggest will stop ALL logging. I still want to get all other errors and warnings from http module. I just want to filter a specific message ("http: TLS handshake error from..."). Your link to Can I replace the existing logger with some custom logger that allows me to filter before output? This is how my log currently looks like: All of them are messages caused by scanners, robots and attacks who do either use the IP instead instead of the domain or do not support TLS1.2 or 1.3 or use incorrect TLS implementations. I want to get rid of these TLS Handshake error messages only. Other things should stay. |
Beta Was this translation helpful? Give feedback.
-
|
You probably need to create wrapper implementing and assign that writer inside s = http.Server{
Addr: serverAddress,
Handler: e, // set Echo as handler
ErrorLog: log.New(new(YourCustomFilterWriter{}), "echo: ", 0),
} |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I will try that! |
Beta Was this translation helpful? Give feedback.
-
|
Okay, I solved it like this: I created a file filterLogger.go with this content: I then use it like this: Of course, you have to do all the surrounding stuff... |
Beta Was this translation helpful? Give feedback.
Answer selected by
Kukulkano
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think those messages are logged by http server logger. You could try to set
http.Server.ErrorLogor global logger to discard inputThis is how you can set
ErrorLogand here is example for autoTLS with http.Server https://echo.labstack.com/cookbook/auto-tls/#server check
customHTTPServerfunction