Fix: [ATS 9.2.x: 200 response after 302 not cached] (#12369)

[shongkaikai]

fix TrafficServer 9.2.x fails to cache 200 responses after 302 redirects despite valid caching headers #12369

[zwoop]

Question: Is this bug only applicable to the 9.2.x branch / version? Is this a back port of a fix on master / 10.x ?

If not, our process says to make the PR against the master branch, and then add the 9.2.x (and 10.x) "Project" identifier to that PR. That tells the respective branch release managers to back port this change.

[shongkaikai]

Question: Is this bug only applicable to the 9.2.x branch / version? Is this a back port of a fix on master / 10.x ?

If not, our process says to make the PR against the master branch, and then add the 9.2.x (and 10.x) "Project" identifier to that PR. That tells the respective branch release managers to back port this change.

Our testing confirms this issue (200 responses after 302 redirects not being cached) exists across all branches:
9.2.x
10.x
master

Main fix submitted to master: master pull request

[zwoop]

I'm going to close this PR, in favor of the master PR: #12373