WordPress/NGINX bug

[sjvn]

One of my colleagues was trying to implement it in his WordPress configuration when...

Nginx doesn’t always tell WordPress that robots.txt is being requested. You have to hack the nginx config. So if the RSL folks are thinking robots.txt is the gateway to their system, lots of machines won’t work out of the box

Once you get to the point that web server configs have to be diddled, your really simple becomes ouchy.

I built code to feed license.xml virtually from WordPress and then to feed robots.txt the same way (default WordPress behavior, rather than hard-coding files in the filesystem). But I need to hand enable location = /robots.txt {
allow all;
log_not_found off;
access_log off;
try_files $uri /index.php?$args;
}
according to the chatbot to make it feed the file. Once you’re hacking server configs, all bets are off.

So, at best, it’s a percentage of sites that can do this out of the box.

I just tried it on one of my WP sites powered by NGNIX and ran into the same thing.

[eckartwalther]

If helpful, Wordpress released a pre-release/alpha version of their support for RSL: https://github.com/Jameswlepage/rsl-wp