The secure CMS.

Welcome to Geeklog, Anonymous Saturday, December 21 2024 @ 09:54 pm EST

Geeklog Forums

url_rewrite, staticpages, and RH 9

 New Topic  Post Reply
 10/10/03 12:33pm (Read 2,536 times)  
Status: offline

hubersan

Forum User
Newbie
Registered: 12/17/01
Posts: 12
Location:Denver, CO
So, my old server (RH 7.2) that worked quite happily crashed a while back, and I rebuilt it with RH 9. One thing that I noticed very quickly is that url_rewrite wasn\'t working correctly... I would get the 404 page instead of the correct staticpage. I just turned off url_rewrite as a quick fix, but I\'d like to turn it back on. I\'m using the default RH9 packages (PHP 4.2.2, MySQL 3.23.58, and Apache 2.0.40). Anyone know why it won\'t work?
 Quote
 10/10/03 08:40pm  
Status: offline

destr0yr

Forum User
Full Member
Registered: 07/06/02
Posts: 324
i remember reading a post that RH9 came with \"bad apache/php\" packages. if you run the up2date and do all the updates, try it again and it should work.
-- destr0yr
"I love deadlines. I like the whooshing sound they make as they fly by." -- Douglas Adams
 Quote
 10/11/03 12:07am  
Status: offline

hubersan

Forum User
Newbie
Registered: 12/17/01
Posts: 12
Location:Denver, CO
unfortunately, that didn\'t work.. I\'ve gotten them all to the latest that RedHat offers.. I\'d PREFER not to recompile everything from scratch, as this is a server with customers on it (I\'m a sysadmin for an ISP), and don\'t feel like dealing with customers complaining because I forgot to compile in feature X. As for RH9 coming with broken apache/php, it would definately not surprise me.. it\'s happened before. I\'d almost believe, past PHP just being broken, that it\'s a ini problem, but again, it\'s pretty stock. :/
 Quote
 01/05/04 02:19pm  
Status: offline

hubersan

Forum User
Newbie
Registered: 12/17/01
Posts: 12
Location:Denver, CO
It's a problem with Apache 2.0 and GL 1.3.8.. from the 2.0 upgrade doc:

Text Formatted Code
The handling of PATH_INFO (trailing path information after the true filename) has changed for some modules. Modules that were previously implemented as a handler but are now implemented as a filter may no longer accept requests with PATH_INFO. Filters such as INCLUDES or PHP are implemented on top of the core handler, and therefore reject requests with PATH_INFO. You can use the AcceptPathInfo directive to force the core handler to accept requests with PATH_INFO and thereby restore the ability to use PATH_INFO in server-side includes.
 


So, add the AcceptPathInfo On line in, and it works great!
 Quote
 New Topic  Post Reply
All times are EST. The time is now 09:54 pm.
  • Normal Topic
  • Sticky Topic
  • Locked Topic
  • New Post
  • Sticky Topic W/ New Post
  • Locked Topic W/ New Post
  •  View Anonymous Posts
  •  Able to post
  •  Filtered HTML Allowed
  •  Censored Content