Home / server / Questions

Questions[wildcard](server)

Martin Hope
user156477
Asked: 2016-10-14 00:35:10 +0800 CST
  • 29

The Nginx config I have throws 404 for .php like:

## Any other attempt to access PHP files returns a 404.
location ~* ^.+\.php$ {
    return 404;
}

However I have some index.php file in subfolder that I want to run. The current config is like:

location = /sitename/subpage/index.php {
    fastcgi_pass phpcgi; #where phpcgi is defined to serve the php files
}

location = /sitename/subpage2/index.php {
    fastcgi_pass phpcgi; 
}

location = /sitename/subpage3/index.php {
    fastcgi_pass phpcgi; 
}

it works perfectly, but the issue is duplicate locations and if there are lots of subpages then the config becomes huge.

I tried the wildcard like * and some regex, which says the nginx test passed but doesn't load the page i.e. 404. What I tried are:

location = /sitename/*/index.php {
    fastcgi_pass phpcgi;
}

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

Is there any way I can have some pathname in the location as regex or wildcard?

nginx regex wildcard
Martin Hope
rorygilchrist
Asked: 2011-03-22 09:32:20 +0800 CST
  • 36

I've just installed Nginx on my server and am extremely happy with the results, however I still cannot figure out how to insert wildcard virtual hosts.

This is the [directory] structure I'd like:

-- public_html (example.com)
---subdoamin 1 (x.example.com)
---subdomain 2 (y.example.com)

As you can see it's pretty basic, however, I'd like the ability to add domains by simply adding an A record for a new subdomain, which will instantly point to the subdirectory of the same name under public_html.

There's stuff on the web, however I haven't come across something exactly like this.

Any help would be greatly appreciated.

subdomain virtualhost nginx wildcard
Martin Hope
Sled
Asked: 2010-03-16 11:47:48 +0800 CST
  • 73

Is the expansion of a wildcard in Bash guaranteed to be in alphabetical order? I am forced to split a large file into 10 Mb pieces so that they can be be accepted by my Mercurial repository.

So I was thinking I could use:

split -b 10485760 Big.file BigFilePiece.

and then in place of:

cat BigFile | bigFileProcessor

I could do:

cat BigFilePiece.* | bigFileProcessor

in its place.

However, I could not find anywhere that guaranteed that the expansion of the asterisk (aka wildcard, aka *) would always be in alphabetical order so that .aa came before .ab (as opposed to be timestamp ordering or something like that).

Also, are there any flaws in my plan? How great is the performance cost of cating the file together?

bash files wildcard large-data