Problem with Apache HTTP 302
If you don't receive any replies from the board can you log this as a ticket with RSA Customer Support and we can look at rolling this into a future ESU if this is a defect. Nathan
It appears that the only issue is not status 302. The current Apache Web Server doesn't parse some Status 200's as well. Additionally, and more critically, the default "GET" message ID (00100) does not parse the User Agent, Cookie, Referrer, or Referrer Domain, all of which are included in the message. It's possible that future content updates fix this issue, but at the moment I don't believe we're that far behind. Any insight?
Would it be possible to share sample events with RSA exported from enVision? If so please email me @ firstname.lastname@example.org and I can provide a SFTP site for upload. Nathan