ericholguin opened a new issue, #7134:
URL: https://github.com/apache/trafficcontrol/issues/7134

   <!--
   ************ STOP!! ************
   If this issue identifies a security vulnerability, DO NOT submit it! 
Instead, contact
   the Apache Traffic Control Security Team at 
[email protected] and follow the
   guidelines at https://apache.org/security regarding vulnerability disclosure.
   
   - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack 
(https://s.apache.org/tc-slack-request)
   or the Traffic Control Users mailing list (send an email to 
[email protected] to subscribe).
   - Before submitting, please **SEARCH GITHUB** for a similar issue or PR
       * https://github.com/apache/trafficcontrol/issues
       * https://github.com/apache/trafficcontrol/pulls
   -->
   
   Currently, if a user's cookie is expired or has an incorrect signature these 
will log as errors in error.log, however this is normal functionality and a 
user error not a system error that needs to be logged in error.log.
   
   <!-- Do not submit security vulnerabilities or support requests here - see 
above -->
   ## This Improvement request (usability, performance, tech debt, etc.) 
affects these Traffic Control components:
   <!-- delete all those that don't apply -->
   
   - Traffic Ops
   
   
   ## Current behavior:
   <!-- Describe how the current features are insufficient. -->
   error.log:
   ```
   ERROR: api.go:263: --- error parsing cookie: bad signature
   ERROR: api.go:263: --- error parsing cookie: signature expired
   ```
   
   ## New behavior:
   <!-- Describe how this change would improve Traffic Control -->
   
   The error's above should no longer appear in error.log
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to