[wp-hackers] Need Help, I cannot figure this out.

Fri Feb 5 19:19:01 UTC 2010

If 'about' didn't exist, it shouldn't have returned a 301 in the wget/log
request where it redirected to the 12 minutes post - it should have returned
a 404, right?

Check the posts table for the post_name of 'about' in the db and see if
there is some type of redirect code or other content/code that is causing
the redirect.  If 'about' truly doesn't exist in the posts db table, then it
could be something else that is causing the redirect.   Your 404 page seems
to return the appropriate status, so this still seems to point to either a
content or plugin issue.   Hopefully nothing malicious, but maybe?

#1 Server Response: http://www.mrsec.com/fdjaklfjdklasfHTTP Status
Code <http://www.seoconsultants.com/tools/headers.asp#status-codes>:
HTTP/1.0 404 Not Found
Date: Fri, 05 Feb 2010 19:17:33 GMT
Server: Apache/2.2.9 (Debian) DAV/2 PHP/5.2.6-1+lenny4 with
Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g mod_perl/2.0.4 Perl/v5.10.0
X-Powered-By: PHP/5.2.6-1+lenny4
X-Pingback: http://www.mrsec.com/xmlrpc.php
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Fri, 05 Feb 2010 19:17:33 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8

On Fri, Feb 5, 2010 at 1:06 PM, Jeremi Bergman <jeremib at gmail.com> wrote:

> >
> > In my example, I was able to request (from lwp-request) the URL "/about"
> > and
>
> was served "/story/about-12-minutes-of-good-basketball<
> > http://www.mrsec.com/story/about-12-minutes-of-good-basketball>".
>
>
> "about" is not a valid page, it's about-2.  But I dont know what would be
> redirecting it...
>
>  Jeremi Bergman
> 865-951-5354
>
>
> On Fri, Feb 5, 2010 at 1:51 PM, Dave Viner <dave at vinertech.com> wrote:
>
> > In my example, I was able to request (from lwp-request) the URL "/about"
> > and
> > was served "/story/about-12-minutes-of-good-basketball<
> > http://www.mrsec.com/story/about-12-minutes-of-good-basketball>".
> >  Do you see anything in the rewrite logs for that?  I left the date in
> the
> > email (Date: Fri, 05 Feb 2010 16:50:53 GMT) so that you can track it
> > closely.
> >
> > If not, then we're pretty certainly in the issue of WP making that
> redirect
> > happen.  In which case, it would be helpful to know what plugins you're
> > using and what your permalinks settings are.
> >
> > Dave Viner
> >
> >
> > On Fri, Feb 5, 2010 at 9:31 AM, Shane Chambers <knoxpics at gmail.com>
> wrote:
> >
> > > Mike, Dave,
> > >
> > > PHP is sitting at the newest Debian release, with security patches.
> > >
> > > root at server-new: php --version
> > > PHP 5.2.6-1+lenny4 with Suhosin-Patch 0.9.6.2 (cli) (built: Nov 22 2009
> > > 01:50:58)
> > > Copyright (c) 1997-2008 The PHP Group
> > > Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies
> > >   with XCache v1.2.2, Copyright (c) 2005-2007, by mOo
> > >   with Suhosin v0.9.27, Copyright (c) 2007, by SektionEins GmbH
> > >
> > > Apache logs the correct request, at least for all the times I've gone
> > > looking at it.  (which is quite a few times)
> > >
> > > I've looked though the rewrite logs, and couldn't find anything
> > conclusive.
> > >  Nothing referencing changing say "tags/vanderbilt" to anything having
> to
> > do
> > > with feed.  (that's why the RewriteLogLevel was set to 9, I wasn't
> seeing
> > > anything at 3, so I bumped it up to max logs)
> > >
> > > The rest is going to have to wait for Jeremi to chime in about.
> > >
> > > Shane
> > >
> > >
> > > Mike Little wrote:
> > >
> > >> Jeremi
> > >>
> > >> A couple of things to check, when the wrong page is delivered, e.g.
> rss
> > >> feed
> > >> instead of about page, what does the apache log record? It will likely
> > be
> > >> difficult to check when the site is busy but looking for a know ip
> > address
> > >> at a specific time will help you tie it down. Does the apache log
> record
> > >> the
> > >> the request was for about or for the feed? If for the about page, then
> > you
> > >> can rule out external, influences. I suspect you have got to that
> stage
> > >> already.
> > >> The next thing is to tie that request in with the rewrite logs  - I
> > think
> > >> Shane has already determined that things look ok.
> > >>
> > >> So you are probably back to something going wrong within WordPress'
> > >> execution chain.
> > >>
> > >> It may be a shot in the dark, but I once had a vaguely similar issue
> > with
> > >> a
> > >> client's site. In this case the page title was being set to the wrong
> > >> thing.
> > >> So the home page might  have a title tag of search results! It
> > >> was intermittent (but was then cached by a front end caching server!)
> > but
> > >> was defintiley happening under high load.
> > >>
> > >> I had just enabled All in one SEO plugin, and when I turned it off
> > again,
> > >> it
> > >> went away.
> > >>
> > >> I think it was going wrong because AIOSEO does whole page buffering
> and
> > I
> > >> believed that there might be a threading issue  with specific versions
> > of
> > >> PHP and output buffering. So that the buffered contents of one request
> > >> were
> > >> returned to the code running a different request. In my case the site
> > was
> > >> running an out of date version of PHP, and running on Windows.
> > >>
> > >> I see you are not running on Windows, but I think it is worth checking
> > >> these
> > >> two things.
> > >> Are you running a plugin that does lots of output buffering?
> > >> and is your version of PHP up-to-date?
> > >>
> > >> Another thing I would try: When you get a wrong page - save the HTML
> and
> > >> headers. Then access the page you received directly and save the HTML
> > and
> > >> headers. Compare the two pairs (possibly ignoring time stamps). If
> they
> > >> are
> > >> identical, then the error may well be in the template/redirection
> logic
> > >> within WordPress and it's plugins.
> > >> If they are different, then I would more strongly suspect output
> > >> buffering.
> > >>
> > >>
> > >>
> > >> Hope this helps,
> > >>
> > >>
> > >> Mike
> > >>
> > >>
> > > _______________________________________________
> > > wp-hackers mailing list
> > > wp-hackers at lists.automattic.com
> > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>