You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@trafficserver.apache.org by "zwoop (via GitHub)" <gi...@apache.org> on 2023/09/21 23:31:50 UTC
[GitHub] [trafficserver] zwoop commented on pull request #10491: Coverity 1518592: check cachekey valid
zwoop commented on PR #10491:
URL: https://github.com/apache/trafficserver/pull/10491#issuecomment-1730488315
I'm generally fine with this, except, makes you wonder how we are even starting up with a configuration that could create broken (invalid) cache keys? Seems we ought to error out if so, rather than just marking it invalid ?
--
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: github-unsubscribe@trafficserver.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org