• While I’m here, perhaps someone can help me with a configuration problem I’m having. I think this is actually an Apache things rather than a WP thing, but someone here may well have encountered and solved it before.
    What I’m seeing is 404 errors for URLs with extra path info, such as perm-links or trakback URLs. So, for example, a URL ending something like …/wp-trackback.php/5 gets a 404, athough …/wp-trackback.php does load correctly.
    Is there an Apache directive I need to specify to fix this? Or can anyone think of any other cause?

Viewing 4 replies - 1 through 4 (of 4 total)
  • I’m no expert, but I did some googling, and found this:

    PATHINFO
    This will not be available if the AcceptPathInfo directive is explicitly set to off. The default behavior, if AcceptPathInfo is not given, is that mod_cgi will accept path info (trailing /more/path/info following the script filename in the URI), while the core server will return a 404 NOT FOUND error for requests with additional path info. Omitting the AcceptPathInfo directive has the same effect as setting it On for mod_cgi requests.

    URIs such as that trackback one with “/something” after the “.php” are fetched by WordPress using PATHINFO. Perhaps it has been turned off for your server…

    Thread Starter laurie

    (@laurie)

    You nailed it! I threw ‘AcceptPathInfo On’ into a .htaccess file and boom, everything working ?? Thanks very much for that.

    I am using a free account on 1and1.com, and I have the same problem. However, I do not think this is the solution, because when I attempt to put AcceptPathInfo On into the .htaccess file, it screws everything up and no pages are served up at all. It turns out that they are using an older version of Apache which does not have this directive.
    Apparently, also, this version runs PHP through CGI (whatever that means exactly) and this is what is causing the problem.

    I posted the post right above this one, and I am reporting that I fixed the problem by hacking the code minimally to replace the / at the end of the trackback URL with a ?p=.
    However, at this point I decided to download the *newest* stable version, which I didn’t have, apparently (I had 1.2), and I see that 1.2.1 has nicely fixed the problem by using rewrite rules in .htaccess to create the trackback URL by simply adding “/trackback” to the permalink URL for the relevant post. Not only does this solve the problem and make things more uniform, it is much nicer for an outside user who only needs to copy one url instead of two when making a post that post refers to the wordpress post and also trackbacks it. That is a relief.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Perma-links, trackback not working’ is closed to new replies.