Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Server
User Name
Linux - Server This forum is for the discussion of Linux Software used in a server related context.


  Search this Thread
Old 09-06-2019, 09:48 AM   #16
LQ Newbie
Registered: Sep 2019
Posts: 1

Rep: Reputation: Disabled

You cannot set a priority, that's why you may get unpredictable results. Given a URL, both modules will examine it and see if they need to do something. So the URL can be changed/not changed by mod_speling and after passing through mod_rewrite it can be changed/not changed again and so on. When one of the 2 modules stops changing the URL, the other one will make another pass and will stop too.
I am totally astonished by this revelation!

Yes I know this is an old thread, but for years and years I've been trying to figure out why mod_speling has never worked for me on any of my servers even though I have always configured it properly. So today I was once again using google to try and find an answer, and I finally ran across this thread, which theoretically explains why mod_speling has always failed for me.

BTW, this is the only resource on the Internet that I have ever found that actually explains the conflict between mod_rewrite and mod_speling! There may be others, but the Apache foundation never mentions this issue in any of their documentation (or if they mention it I certainly have never found it).

It also seems crazy that in this day and age we have NO WAY of using both mod_speling and mod_rewrite on the same server. It seems even more crazy that the conflict between these two modules is so poorly documented.

Or is there a way to use them both now, but this thread does not explain how, perhaps because it's an old thread ???

From my apparently limited way of thinking, it would seem that putting my mod_speling directives into the httpd.conf file and then putting my mod_rewrite directives into a directory block that's inside a virtual host block *might* make Apache do the mod_speling changes first -- since the directives in httpd.conf apply to all requests. Then when Apache moves on to the vhost block it would do that stuff later -- on the lettercase-corrected URL and not on the original URL.

But according to the previous posts in this thread, that's not how Apache works. Which makes me wonder why there is still no mechanism in Apache to force it to fix the lettercase of a URL first, and then apply mod_rewrite to the lettercase-corrected URL?

I mean, is it really such a stretch of the imagination to expect that an Apache admin might want and need this capability? Because that's all I want to do, and I cannot imagine that this is an uncommon desire.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Its a README curse.. :) (speling mistaike) GTrax General 0 09-18-2010 08:39 AM
Use Of Mod Jk in Apache chnlinux Linux - Newbie 0 04-02-2008 01:53 AM
mod speling not working in apache2.2? lykwydchykyn Debian 1 08-15-2007 09:57 AM
Apache 1.3.xx mod's DaRk RuSs General 0 07-07-2004 09:49 PM
apache mod rewrite Robert0380 Linux - Software 5 07-31-2003 04:42 PM > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 08:05 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration