ansaurus

Question

Answer 1

A:

Try an absolute replacement:

RewriteRule ^([^\ ]*)\ (.*) /$1_$2 [N]

Gumbo 2009-11-05 13:13:37

No, that doesn't work, same result. I circumvent it now with a condition: `RewriteCond %{REQUEST_FILENAME} .*[\ ].*`

Boldewyn 2009-11-05 13:20:44

@Boldewyn: It works for me this way.

Gumbo 2009-11-22 22:08:10

Answer 2

+2 A:

UPDATE

looking at your update 3 (helpful, thanks), 2 more ideas come to my mind:

there is an apache issue: *mod_rewrite adds path info postfix after a substitution occured*, that looks similar to yours. this was fixed in 2.2.12 with the introduction of the discardpathinfo|DPI RewriteRule flag. try adding this flag to your RewriteRule:
```
RewriteRule (.*)[\ ](.*) $1_$2 [N,DPI]
```
and see if that solves the issue. needs apache 2.2.12.
do you happen to have mod_dir enabled an DirectorySlash On? try disabling it.

UPDATE END

your setup:

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} .*[\ ].*
RewriteRule (.*)[\ ](.*) $1_$2 [N]

works for me (http://localhost/test/This is an example.html, rewrite rules in VirtualHost config, apache 2.2.14). here is my RewriteLog (with RewriteLogLevel 2):

init rewrite engine with requested uri /test/This is an example.html
rewrite '/test/This is an example.html' -> '/test/This is an_example.html'
rewrite '/test/This is an_example.html' -> '/test/This is_an_example.html'
rewrite '/test/This is_an_example.html' -> '/test/This_is_an_example.html'
local path result: /test/This_is_an_example.html
prefixed with document_root to D:/var/www/test/This_is_an_example.html
go-ahead with D:/var/www/test/This_is_an_example.html [OK]

when D:/var/www/test/This_is_an_example.html does not exist, i get a 404 - but no segfault.

could you post your RewriteLog? where do you put your rewrite rules? into an .htaccess? do you have any directives (AliasMatch etc.) that also work on your url?

ax 2009-11-20 06:51:39

It works for me too, when I add the RewriteCond. The question however is, why do I need the RewriteCond at all? If you look at my RewriteRule in the question, it should loop round and round until no space is left, and that without need of a RewriteCond. My question is, why doesn't it do it.

Boldewyn 2009-11-20 07:58:44

it also works here without the `RewriteCond` (same `RewriteLog`). so again: what does your `RewriteLog` look like, are your rewrite rules in an `.htaccess`, and/or are there other directives matching the url in question?

ax 2009-11-20 09:37:27

The rewrite rules are in an .htaccess file. Please note my first update in the question, the segfault only occurs, if there is a folder-like component before the rule. I'll paste a bit of the rewrite log above into the question.

Boldewyn 2009-11-21 21:14:49

thanks for the log. see my update for another idea.

ax 2009-11-22 10:37:11

Wow, thanks for digging up the bug. It really looks like my problem. Unfortunately I still have 2.2.11, but I'll try and set up 2.2.12 to verify this, before the bounty expires.

Boldewyn 2009-11-22 21:30:46

Yep, that bug was the problem. Now I'm gonna print out this question, frame it and put it on the wall. In the end, how many mod_rewrite questions on SO end with: "It's not your fault, it's a bug in mod_rewrite"? ;-)

Boldewyn 2009-11-23 07:25:56

Answer 3

A:

By and large, the Apache developers will take a SIGSEGV in httpd quite seriously if presented with a repeatable test case. Even more so if you attach a debugger and capture a backtrace.

bmargulies 2009-11-22 18:39:17

the segfault could probably be disabled with LimitInternalRecursion (Apache 2.0.47+) or RewriteOptions MaxRedirects (2.0.45-46)

ax 2009-11-22 19:41:25

ansaurus

tags:

views:

answers:

Apache: RewriteRule leads to segfault

related questions