You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could implement logging to capture and analyze requests made to specific subdomains on our website, such as cyb.no, bong.cyb.no, and oko.cyb.no. This will allow us to monitor which redirects and subdomains are actually in use (and remove those that are not).
We should count the number of requests made to each of these domains. For instance, using a grep command to filter the log file and wc -l to count the occurrences.
The logs need to be purged regularly.
We use Caddy as a web server. Something like this could work:
{
# Global options
log {
output file /var/log/caddy/domain_specific.log
format single_field "{host} {uri} {status}"
}
}
bong.cyb.no, cyb.no, oko.cyb.no {
# Specific configuration
log {
output file /var/log/caddy/domain_specific.log
format "{host} {uri} {status}"
}
}
The text was updated successfully, but these errors were encountered:
We could implement logging to capture and analyze requests made to specific subdomains on our website, such as
cyb.no
,bong.cyb.no
, andoko.cyb.no
. This will allow us to monitor which redirects and subdomains are actually in use (and remove those that are not).We should count the number of requests made to each of these domains. For instance, using a
grep
command to filter the log file andwc -l
to count the occurrences.The logs need to be purged regularly.
We use Caddy as a web server. Something like this could work:
The text was updated successfully, but these errors were encountered: