Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/1445
I looked at this as well and it definitely looks like it's an artifact of a
remap plugin setting the transaction to be an error. You can see that this
happens in a switch statement where `t_state.next_action` was
`SM_ACTION_REMAP_REQUEST` on entry yet is `SM_ACTION_SEND_ERROR_CACHE_NOOP`.
This could only have been updated via `do_remap_request()` and presumably via a
remap plugin as `RemapProcessor` doesn't update that member. It also seems
reasonable to check if a plugin has error'd out the transaction and give up on
further transaction processing at that point.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
