Ticket #3820 (new defect)

Opened 2 years ago

Last modified 1 year ago

Squid in accelerator mode; Permalink "mod_rewrite" problem.

Reported by: shanefroebel Assigned to: anonymous
Priority: normal Milestone: 2.9
Component: General Version: 2.2
Severity: normal Keywords: squid mod_rewrite
Cc: shane.froebel@gmail.com

Description

Yesterday I installed squid on our main domain, battlestarwiki.org. And our WordPress (Version 2.2), installed at blog.battlestarwiki.org, falls under the domain. When I went to "click" on a link, it brings me back to the "main" index.

http://blog.battlestarwiki.org/2007/02/19/ahoy-matty-i-got-me-a-squid/ is a perfect example. Clicking on the link, does not allow me to view the single post by itself.

We have Mediawiki installed and it works just fine with mod_rewrite.

Thanks for your time. :-)

Change History

02/20/07 20:47:49 changed by foolswisdom

  • priority changed from high to normal.
  • severity changed from blocker to normal.
  • milestone changed from 2.2 to 2.3.

shanefroebel, thank you for participating in WordPress! As WordPress uses the same or very similar mod write rules as other blogging systems, I would be surprised if the fault is WordPress'.

I don't really understand the nature of these problems, but someone on IRC suggested "try 404 handler. probably PATH_INFO is mangled on your side"

Realistically, if the problem is WordPress' it is unlikely be be resolved unless you are able to isolate the problem further.

02/21/07 15:52:42 changed by shanefroebel

Expain.. I don't quite understand what you mean to test.

02/24/07 17:03:37 changed by shanefroebel

Ok.. I've done some digging into the WordPress code itself. When I installed a new version of WordPress on the server, the "URL" for the administration settings "WordPress Address (URL)" and "Blog Address (URL)" came out to be:

http://blog.battlestarwiki.orghttp://blog.battlestarwiki.org/index.php

So this tells me, as Squid reads the installation from Apache, the location paths are not correct when trying to run a rewrite URL. Now squid "acts" as the "processing" point (external IP address) and talks with Apache which is now on 127.0.0.1. So when everything goes through it it changes it's makeup.

Now I looked through the rewrite class, and I can not make heads or tails on how to see how it works. Somewhere in their is where something has to be defined to say "oh, we have squid installed. Goto the right "url/file" location.

I hope that is clear enough.

02/25/07 14:21:07 changed by markjaquith

There should be no index.php in your Blog Address setting.

(follow-up: ↓ 6 ) 02/27/07 14:55:37 changed by shanefroebel

I have had that removed for a while. Doesn't WordPress.com use Squid?

(in reply to: ↑ 5 ; follow-up: ↓ 8 ) 02/27/07 18:14:35 changed by foolswisdom

Replying to shanefroebel:

I have had that removed for a while. Doesn't WordPress.com use Squid?

I asked and the answer is no. The answer of what we do use is likely in our job posting page: Debian/Ubuntu, PHP, MySQL, Litespeed, Pound, Wackamole, Spread, Nagios, Munin, Monit, NFS, Postfix, MyDNS.

02/28/07 18:17:06 changed by shanefroebel

Great :(

(in reply to: ↑ 6 ) 03/01/07 17:20:11 changed by shanefroebel

What file process the "mod_rewrite" requests (i.e. filenames and line numbers) and I could try to work on a fix for us squid needed people.

03/01/07 17:20:24 changed by shanefroebel

  • cc set to shane.froebel@gmail.com.

09/19/07 21:20:10 changed by Nazgul

  • milestone changed from 2.3 to 2.5.

11/19/07 15:54:08 changed by Nazgul

See also #3686.