Haven't tested with lua. We noticed the behavior changes when regex_remap is used with header_rewrite.
regex_remap by itself $p is the "original request port" regex_remap with header_rewrite $p is the "origin port" We investigating this at the moment. Would be nice to have regex_remap support the different type or components from an uri. https://en.wikipedia.org/wiki/Uniform_resource_identifier "authority part" for example to keep username:[email protected]:123 or even "hierarchical part" so would just be easier to drop query strings. On Tue, Sep 1, 2015 at 8:57 AM, Jason Strongman < [email protected]> wrote: > Steve, > > Is there any benefit to using this plugin, as opposed to processing > via the lua plugin? > Any performance concerns as load increases? > > > > On Fri, Aug 28, 2015 at 10:02 AM, Steve Malenfant <[email protected]> > wrote: > > Some looked at the code, and seems like this "$p" applies to the "request > > URL" which would be the left side of the remap line. Although from my > > testing, it applies to the origin port (right side). What is the > > expectation? > > > > > https://docs.trafficserver.apache.org/en/latest/reference/configuration/remap.config.en.html > > > > $p - The original port number > > > > The goal here is to to remove any query string and keep the origin port > > defined in the remap line. > > > > Discussion available here : > > https://github.com/Comcast/traffic_control/pull/297 > > > > Some quick details about the configuration... > > > > remap.config : > > > > map http://edge01/ http://origin:8081/ @plugin=regex_remap.so > > @pparam=drop_qstring.config > > > > drop_qstring.config : > > > > /([^?]+) $s://$t:$p/$1 > > > > Old drop_qstring.config (which drops the origin port) : > > > > /([^?]+) $s://$t/$1 > > > > Thanks, > > > > Steve > > > > > > > > > > >
