view mod_admin_web/admin_web/www_files/css/style.css @ 5787:e79f9dec35c0

mod_c2s_conn_throttle: Reduce log level from error->info Our general policy is that "error" should never be triggerable by remote entities, and that it is always about something that requires admin intervention. This satisfies neither condition. The "warn" level can be used for unexpected events/behaviour triggered by remote entities, and this could qualify. However I don't think failed auth attempts are unexpected enough. I selected "info" because it is what is also used for other notable session lifecycle events.
author Matthew Wild <mwild1@gmail.com>
date Thu, 07 Dec 2023 15:46:50 +0000
parents f53475ee7ff4
children
line wrap: on
line source

body {
  margin: 0
}

a {
  color: #0000FF
}

#adhocCommands > ul {
  margin: 0
}

.btn {
  margin-right: 0.3em
}

.btn:last-child {
  margin-right: 0
}

#log_container {
  clear: both;
  display: none
}

#adhocCommands {
  border-right: solid 1px
}

#adhocCommands li {
  list-style: inside
}

#login {
  float: left;
  margin: 1em 2em 0 1em;
  padding-right: 1em;
  border: solid 1px;
  background: #eef0f2;
  color: #000000
}

#main {
  display: none;
  margin: 1em
}

#main p {
  margin: 0
}

#top {
  clear: both;
  width: 100%;
  padding: 0;
}

@media screen and (min-width: 757px) {
  #header {
    background: url(../images/blue_orange.png) repeat-x
  }
}

#header img {
  max-width: 100%;
  height: auto
}

#menu {
  display: none;
  color: #454748;
  font-size: 1.1em;
  background: #eef0f2;
  width: 100%;
}

#menu ul {
  display: inline;
  list-style-type: none;
  margin: 0;
  padding: 0.5em 0
}

#menu li {
  display: inline;
  padding: 0 0.5em
}

#menu a {
  color: #454748;
  text-decoration: none
}

#menu li a:hover {
  color: #6197DF;
  text-decoration: underline
}

#selector {
  display: inline-block
}

#s2sList h2, #c2sList h2 {
  color: #4b8ade;
  margin: 0
}

#s2sList li, #c2sList li {
  cursor: pointer
}

#host {
  margin: 0.25em;
}