How to check if LocationMatch regex is working

apache-2.4regex

I have location match regex

ScriptAlias /script /var/www/somescript.bash
Action some-handler /script virtual
<LocationMatch "/(?:\w+:)?\/\/[^\/]+([^?#]+)/">
    SetHandler some-handler
</LocationMatch>

Now when test that regex https://regex101.com/r/lO0aV1/1 you can see that location is matched but somescript.bash is never executed.

mod_actions are on by the way.

In error log I do not see anything. In access log I got 404.

How can I check that this regex is working? Is there anyway that I can log that?

Best Answer

Make a CustomLog, with e.g.:

CustomLog "/var/log/httpd/mylog.log" "%h %l %u %t \"%r\" %>s %b what:%{INDICATOR_VAR}e"

and use SetEnv to set the INDICATOR_VAR:

<LocationMatch ...>
    SetEnv INDICATOR_VAR "OK"
</LocationMatch>

Related Solutions

Php – RegEx Match URL Pattern

What language are you using?

In general it sounds like you want something that matches the basic aspects of a domain, ruling out the possibility of a period other than the one that delinates the .tld.

#http://[^.]+\.(com|net|org)#i

If you don't want to match the protocal, maybe something like this.

#[^. ]+\.(com|net|org)#i

Your desire to handle multi-part TLD's will really screw this up, you will need to maintain a manual list of all the ones you want to match. The only alternative is to do DNS lookups to determine the listing type. There really isn't another way to extract subdomain data from the domain with a regular expression because by rights domains are actually just subdomains of some TLD (top level domain).

Edit: To match TLD's assuming they woudl have less than four characters, you can play around with something like this. You're going to have to work out what constitutes the start and end of a match. Are you requireing the presense of a protocal? Is this in a paragraph where somebody could type.a period out of context? If you give more details on the parameters we might be able to provide a more precise solution.

[^.]+((\.[^.]{0,3})+)

Nginx wildcard/regex in location path

The = modifier in location block is an exact match, without any wildcards, prefix matching or regular expressions. That's why it doesn't work.

On your regex attempt, [a-z] matches a single character between a and z. That's why it doesn't work for you.

You need to have your locations set up like the following. Note the order of location statements. nginx picks the first matching regex condition.

location ~ ^/sitename/[0-9a-z]+/index.php$ {
    fastcgi_pass phpcgi;
}

location ~ \.php$ {
    return 404;
}

I use case sensitive matching here (~ modifier instead of ~*). In the first case, I match the first part of path, then one or more number of alphabetic / number characters and then index.php. You can modify the match range, but remember the + for "one or more" repetitions.

The second one matches any URI ending with .php. You don't need the extra characters in your version because of the way regular expressions work.

Best Answer

Related Solutions

Php – RegEx Match URL Pattern

Nginx wildcard/regex in location path

Related Topic