This didn't happen with Apache 2.0, and, according to the MediaWiki people, doesn't happen to them with 2.2 either.

So I've been thinking it could be an issue with the Windows port of Apache 2.2 or PHP (and BTW, it happens with 2.2.0 and PHP 5.1.2 too; I just updated to see whether it was fixed on the cutting edge versions).

Normaly it should work like in 2.0.x . I had programmed something in PHP that is like that URL. On my server it works (2.2.x and 2.0.x)

Maybe you used mod_rewrite in 2.0.x ?

There is something you can try. If you installed the 2.2.x in the same directority as the 2.0.x make a backup from the 2.2.x httpd.conf and use the old one from 2.0.x (if nessary change the pathes in the old httpd.conf)

Maybe you need to comment out some include files in the httpd.conf The configs had changed a bit. There are some file in the conf/extra folder now.

I'm not using mod_rewrite. I use a few aliases, but I don't think that's the problem.

I can try to compare the old httpd.conf file with the 2.2.0 one (though the horrible breaking of httpd.conf into extra/* makes it a bit more difficult), but I don't think it is a setup issue. As I've said, people with similar setups on Apache 2.2.0 running on GNU/Linux do not experience the problem.

I've been reading an old (c. 2003) thread on the Apache developer's list that talks about this very problem.

The APR lib (on Windows) thinks that colon is not valid in a filename, which is correct. However, the module generating the path should inform Apache that it takes care of the path and that it shouldn't need to be mapped to the filesystem.

I did not use an installer. I downloaded it and installed it manually.
------
edit:
Now I got the same error. But the wiki runs. I think you can ignore the error. The error is caused by the url, cause it contains the dobblepoint :
Apache knows that no file can have this name. But that is for the Database.
I think, but haven't testet yet, with mod_rewrite it should work without any error.

Yes, I know that I the wiki runs. However, this shouldn't happen. There's no point in Apache detecting that it cannot map the path to the filesystem; it should be informed that the path is being processed elsewhere.

And yes, I can ignore it, but I would rather not. I run that Apache on a USB stick, and I don't want unnecessary writes, so I've set it up to log only the most critical errors. Accessing Special pages in MediaWiki is hardly critical

All in all, the thing didn't happen in Apache 2.0 and doesn't happen on non-Windows environments, so it is a bug somewhere.

Who said anything about Spanish, smart guy? My error message would clearly be different than his as I have different wiki topics than he does.

tdonovan wrote:

I do not experience this problem with MediaWiki version 1.11.0, in either English or Spanish.
I am using Apache 2.2.4 (from Apache Lounge) and mod_fcgid with PHP 5.2.2 and MySQL 5.0.48.

All Special-Pages links now properly go to URIs like /wiki/index.php?title=Special:Specialpages instead of /wiki/Especial:SpecialPages - either from Portata (Spanish) or Main Page (English).

That's because you appear not to be using Well Designed URLs which is something, given the topic of the wiki, is not an option for me to consider, and ideally one nobody would ever consider. Your wiki that uses "title=" is less usable than one that uses clean URLs for Mediawiki and omits the title from the URL; as such your wiki does a disservice to your users.

tdonovan wrote:

re: "This is embarassing for Apache."
I don't think Apache is likely to be embarrassed by MediaWiki bugs.

It is not a Mediawiki bug, it is a bug in Apache and has been documented as such as Bug 41441 in ASF Bugzilla.

So I repeat: it is a bug, it worked in Apache 1.3, and IIS does not have this problem so it is embarassing the Apache 2.2 does. The question was, is it going to be fixed? It can't be difficult.

Those are MediaWiki-generated URLs - not mine. Portada is "Main Page" in Spanish, not a topic.
That is also why the original poster's incorrect URL was /wiki/Especial:SpecialPages rather than /wiki/Special:SpecialPages.

Like the original poster, lektu, I was not using mod_rewrite. I used the default MediaWiki configuration to test - not the "better ideas from welldesignedurls.org" config. The instructions do not appear to be appropriate to WikiMedia 1.11.0. There is no reference to $wgArticlePath in LocalSettings.php for version 1.11.0.

re:"Am I going to have to revert to using IIS" - That would be my recommendation.

Those are MediaWiki-generated URLs - not mine. Portada is "Main Page" in Spanish, not a topic. That is also why the original poster's incorrect URL was /wiki/Especial:SpecialPages rather than /wiki/Special:SpecialPages.

I'm confused, you were the one who brought up the spanish aspect, not me. Why did you bring it up when it wasn't part of the issue?

Quote:

Like the original poster, lektu, I was not using mod_rewrite. I used the default MediaWiki configuration to test - not the "better ideas from welldesignedurls.org" config.

Maybe you should test with mod_rewrite then? It is what Wikipedia uses.

Quote:

The instructions do not appear to be appropriate to WikiMedia 1.11.0. There is no reference to $wgArticlePath in LocalSettings.php for version 1.11.0.

I don't know about that, the instructions were written last year, something to update maybe. But that's not the point, the point is fixing the bug in Apache to allow for well designed URLs.

Quote:

re:"Am I going to have to revert to using IIS" - That would be my recommendation.

That was a rhetorical question to point out deficiencies in Apache, the software so many present as if it were above comparison to IIS. I'd like Apache to be better than IIS, and that's why I asked about this documented bug being fixed.