Do you know if anyone has documentation on creating a rewrite rule with Lucee and Linux to remove index.cfm from the URL? I have tried various rules, but they all result in a 404 error and I suspect that the server does not redirect the request to Lucee for processing.

Try this <IfModule mod_rewrite.c> RewriteEngine On # Remove CFML extension and redirect to clean URL RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME}\.cfm -f RewriteRule ^(.+)\.cfm$ /$1/ [R=301,L,QSA] # Transform query string parameters to path segments RewriteRule ^(.+)/([^/]+)/([^/]+)(/.*)?$ %{REQUEST_URI}?r=$2&m=$3 [L,QSA] # Serve actual CFML files internally RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.+)$ $1.cfm [L,QSA] </IfModule> First, enable URL rewriting in your Lucee Server Administrator Navigate to Web Context → URL Mapping Enable "URL Rewriting" Set "URL Separator" to "/" Ensure mod_rewrite is enabled in Apache Test thoroughly with different URL structures Consider adding error handling for invalid URLs Monitor server logs for rewrite issues Remember that Lucee's built-in URL rewriting handles CFML-specific routing

Hey Gregory, not sure how you are doing this now. Maybe using a rewrite valve in Tomcat, no idea. It can be handled with a Tomcat rewrite valve, but you do have other options. One way is to use CommandBox which allows you to attach a rules.json file to your server.json file. This is probably the easiest way, I'm sure someone at Ortus can help you there. Another way is to use a Lucee docker image that comes pre-packed with Ngnix. This way, you can create your rewrite rules before it hits Lucee.

@Gregory Alexander Rewriting isn't something CF does, it's performed by your web server and the process differs based on the server

Thanks, everyone! I will try to implement the rewrite setting in Lucee!

@Gregory Alexander Well, that's not entirely true. Lucee is not a web server, so you can't use "plain Lucee" to run a website

FWIW, Tuckey is sadly abandonware. There hasn't been a real release in many many years and it's been dropped by the author.

Hi Alholden, Yes, Brad is correct in his response. It is for SEO purposes. GSR, do I need to switch to multi-mode to edit the web context in Lucee? Everytime I click on the web context link it opens up a new Lucee window. Thank-you everyone! I will get to this over the weekend, you're all great!

I see "abandonware" as an opportunity.

Ha, well yes. We actually maintained a fork of Tuckey for a while which had fixes in it we needed since the main project had stopped merging pulls.

No you do not need multi mode for this

Thanks gsr, I can't seem to get into any web contexts UI. I suspect I may have to edit the json directly.

@Gregory Alexander What exactly are you needing to do in Lucee's web context. The whole point of single context mode is there is no separate web context. All config is done directly in the server context. Is there a setting you can't find?

Sorry for not responding earlier- I am trying to get a dozen things done- including releasing a new version of Galaxy Blog for Lucee. Brad- I was trying to follow the instructions that GSR gave, ie: "First, enable URL rewriting in your Lucee Server Administrator Navigate to Web Context → URL Mapping Enable "URL Rewriting" Set "URL Separator" to "/"

Yeah, TBH it's a little hard to follow what you've got going on. I have no earthly clue what Lucee setting GSR is speaking of, so I can't help you there. If the raw CF code is coming back from the server, that means Lucee isn't server the file, Apache is. I'd have to understand better exactly what your rewrite rules are doing to the requests as well as how your proxy to Tomcat is configured to really help. Whatever rewrites you have above isn't the standard framework rewrites I'm familiar with

There is no settings required Just follow what I have written and it will work

HI GSR,

i am not sure the setu[p you have but there are ways to fix it, lets take a step by step approach lets do it simple

# Enable mod_proxy in Apache
a2enmod proxy
a2enmod proxy_http

# Restart Apache
service apache2 restart

step 2

<IfModule mod_proxy.c>
    ProxyPreserveHost On
    ProxyPassReverse / <http://127.0.0.1:8888/>
</IfModule>

<IfModule mod_rewrite.c>
    RewriteEngine On
    
    # Handle existing .cfm files
    RewriteCond %{REQUEST_FILENAME}\.cfm -f
    RewriteRule ^(.+)\.cfm$ <http://127.0.0.1:8888/$1.cfm> [P,L]
    
    # Let Lucee handle clean URLs internally
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.+)$ <http://127.0.0.1:8888/$1> [P,L]
</IfModule>

Add these security rules before your rewrite rules:

# Block direct CFML file access attempts
RewriteCond %{THE_REQUEST} \.cfm[\s/?] [NC]
RewriteRule ^ - [F,L]

# Prevent directory traversal
RewriteCond %{REQUEST_URI} ..+/.* [NC]
RewriteRule .* - [F,L]

Thank-you!