If no auth token is present, do not emit verbose error message

[bbockelm]

If someone does a curl against the metrics endpoint with neither token nor cookie, there's a long error message that's emited. We should only have debugging information when there's a reasonable chance that someone was trying to authenticate.

@haoming29 - can you take a look at this? It was irritating me as the current director does not even try to authenticate yet queries my /metric endpoint at the rate of about 2Hz, causing 1-2 dozen log lines per second when I'm trying to debug.

[haoming29]

If someone does a curl against the metrics endpoint with neither token nor cookie, there's a long error message that's emited. We should only have debugging information when there's a reasonable chance that someone was trying to authenticate.

@haoming29 - can you take a look at this? It was irritating me as the current director does not even try to authenticate yet queries my /metric endpoint at the rate of about 2Hz, causing 1-2 dozen log lines per second when I'm trying to debug.

I agree that we should not produce verbose log message when there's no token present, but I can't reproduce your issue where the director didn't try to authenticate against /metrics url. Which director are you referring to? Is that a local/dev version or some director on our test instance? Which /metrics endpoint is the director accessing? The internal one or the one for an origin? and what's your steps to reproduce?

[haoming29]

LGTM. It might worth a separate issue for the director's unauthed behavior