Forum Discussion
eric_haupt1
Apr 23, 2019Nimbostratus
Figured it out - it was a portion of an x509v3 cert parse irule that was causing this condition. Reverting to an older version resolved the issue. Not sure of the specific event or cause that was impacting the 302 redirects. I haven't debugged that far into it.