Marc Dirix <[email protected]> wrote: > I've attached the logfile.
Just the backtrace would have sufficed. It confirms my hypothesis: RXML gets executed when a protocol cache entry is being delivered. It's intentional that the RequestID isn't fully populated then, to make the overhead as low as possible in the protocol cache. What happens is that you get an authentication failure through a vary callback when the cached entry is about to be sent, which then starts an rxml evaluation of an auth failure file you have in your site. Somewhere along the line there, Roxen should fill out the RequestID to make it fully operational. The question is where. Could you please open a ticket about it?
