I have a rewrite where we'll be creating a cookie if you're being
redirected from a few specific domains. Is there a way I can use one
variable to handle multiple domains or does the rewrite block need to be
repeated based on the domain? I'd like one block to be able to be directed
to handle 3-4
e URL does not contain query string
RewriteCond %{QUERY_STRING} !.
RewriteCond %{REQUEST_URI} ^(.*)
RewriteRule ^.*$ ${rdm:%1} [R=301,L]
On Mon, Jan 19, 2015 at 4:34 PM, Doug Strick
wrote:
> I'm working on adding some 301 redirects for some sites we're migrating.
> I've been gi
I'm working on adding some 301 redirects for some sites we're migrating.
I've been given a large list of 1:1 redirects. The majority of URLs
include a query string. I've included the the full 1:1 URL mapping list in
my redirect map text file. I'm finding issues when testing the URLs that
contain
> In 2.4, it seems like you should be able to register mod_substitute
> via mod_filter. mod_filter has a "match" parameter that in 2.4 is an
> ap_expr expression, so it can ready basically anything floating around
> in the server.
>
> mod_filter can be pretty intimidating though.
I really wish I
this module can do as well.
Thanks
SetEnvIf HTTP_COOKIE "(^|)CUST_TYPE=test" parp
On Thu, Apr 17, 2014 at 3:01 PM, Doug Strick wrote:
> I've come up with the below config using mod_ext_filter which isn't
> desirable, but it's the only thing
*
ExtFilterDefine doug mode=output intype=text/html enableenv=FILTER \
cmd="/bin/bash /apps/httpd/scripts/replace.sh"
SetOutputFilter doug
*replace.sh*
#!/bin/bash
/bin/sed -r 's/http\:\/\//https\:\/\//g'
On Wed, Apr 16, 2014 at 10:23 AM, Doug Strick wrote:
&
Hello,
I'm looking for a way to modify the data on outgoing requests
conditionally. I've tried using mod_substitute, but that appears to be an
all or nothing module. The documentation for mod_filter says it can be
invoked on environment variables, but it's not exactly clear on the valid
syntax f
