Forum Discussion
daniel_spillers
Aug 09, 2012Nimbostratus
The solution is there, but did anyone ever determine why the HTTP::redirect is being executed within the CLIENT_ACCEPTED context, as the error message states? Why isn't it being executed only within the HTTP_RESPONSE or HTTP_REQUEST contexts?
What is it about using "after" and a timeout period that seems to cause the code to be run in the CLIENT_ACCEPTED context?
I have a similar rule that uses an after that periodically triggers a similar error (only difference is that I'm trying to use HTTP::respond). I put the command in the HTTP_REQUEST context, yet it's being triggered in the CLIENT_ACCEPTED context.