The naming is just coincidence, it's not a transformation plugin, but just a simple plugin that denies/allows requests based on the presence/absence of specific headers. It's a remap plugin because we need different configurations for different mappings, otherwise it could have been a simple header manipulation plugin.
However, I think it may be the case that the TSRemapDoRemap function was activated twice, the second time with an invalid transaction handler, and I will add some code to either prove or disprove this theory. I'll let you guys know in either case. Thanks. Acácio Centeno Software Engineering Azion Technologies Porto Alegre, Brasil +55 51 3012 3005 | +55 51 8118 9947 Miami, USA +1 305 704 8816 Quaisquer informações contidas neste e-mail e anexos podem ser confidenciais e privilegiadas, protegidas por sigilo legal. Qualquer forma de utilização deste documento depende de autorização do emissor, sujeito as penalidades cabíveis. Any information in this e-mail and attachments may be confidential and privileged, protected by legal confidentiality. The use of this document require authorization by the issuer, subject to penalties. On Mon, Aug 18, 2014 at 11:43 AM, Nick Kew <n...@apache.org> wrote: > On Mon, 18 Aug 2014 10:24:02 -0300 > Acácio Centeno <acacio.cent...@azion.com> wrote: > > > [chop] > > Your plugin is called request_filter and appears to involve methods of > a RequestFilter object. Is this a red herring, or does this crash in fact > originate in a filter? > > The reason for the question is that this looks like a close cousin to two > crashes we've encountered recently in filter functions. Maybe the fix > suggested in the thread at > http://comments.gmane.org/gmane.comp.apache.trafficserver.devel/1920 > might be worth a try? > > > -- > Nick Kew >
