The WordPress code looks to be the bog-standard code, as created on WP installation. It has nothing to do with external redirects (it does internal rewriting only).
You need to dig deeper into your stats reports and find out what URLs are returning a 302-Found (a.k.a. 302-Moved Temporarily) server response. If your stats reports can't tell you, then dig into the raw server access logs, and find those URLs.
If the traffic to either those URLs or to the URLs that they redirect to is important to you, and if they have been permanently moved (e.g. moved from www to non-www, or any other known change), then the response must be a 301-Moved Permanently to get the best/proper reaction from search engines.
The next step in this case would be to dig through your server control panel settings and either correct the redirect (from a 302 to a 301) or remove it entirely and then implement the 301 redirect yourself in your .htaccess file.
You can check server responses on a request-by-request basis using the "Live HTTP Headers" add-on for Firefox/Mozilla browsers -- it's good basic kit.
I have add this to the awstats config file:
ExtraSectionName1="Moved temporarily (redirect - 302)"
ExtraSectionFirstColumnFormat1="<A HREF='http://www.your_site.com%s' TARGET='_blank'>%s</A>"
Should add a new section to the log, will tell ya whats going on...
At the moment there's only one entry in the log pointing to site's feeds... maybe a plugin that enables redirecting feeds to feedburner?
I'm having the same situation. Almost 90% of status codes are from 302 moved temporarily in Awstats.
Did you happen to find what's happening?
I had some forum software once that used 302 internally for something or other. Used to run up thousands of 302 redirects.,
[edited by: bouncybunny at 2:31 pm (utc) on Aug. 4, 2009]
Nope no answer yet... I have read something like if the Worpdress admin access causes this, but have no confirmation about it.
Do you use Wordpress as I do?
<If your stats reports can't tell you, then dig into the raw server access logs, and find those URLs.> - JDMorgan
FYI, the how-to for what JDM was saying is to find the 302 lines and look in the referrer field for the URL of the page just before the 302, i.e. the one that had a link to a 302 redirect. Things should become clear then.
220.127.116.11 - - [04/Aug/2009:08:06:17 -0500] "GET /hp-signs-workplace-services-agreement-with-akzonobel HTTP/1.0" 302 - "-" "Sphere Scout&v4.0 - scout at sphere dot com"
18.104.22.168 - - [04/Aug/2009:08:06:18 -0500] "GET /hp-signs-workplace-services-agreement-with-akzonobel/ HTTP/1.0" 200 41519 "-" "Sphere Scout&v4.0 - scout at sphere dot com"
22.214.171.124 - - [04/Aug/2009:08:06:19 -0500] "GET /hp-signs-workplace-services-agreement-with-akzonobel HTTP/1.0" 302 - "-" "Sphere Scout&v4.0 - scout at sphere dot com"
126.96.36.199 - - [04/Aug/2009:08:06:19 -0500] "GET /hp-signs-workplace-services-agreement-with-akzonobel/ HTTP/1.0" 200 41519 "-" "Sphere Scout&v4.0 - scout at sphere dot com"
188.8.131.52 - - [04/Aug/2009:08:00:38 -0500] "GET /feed/ HTTP/1.0" 302 - "-" "Moreoverbot/5.00 (+http://www.moreover.com; firstname.lastname@example.org)"
184.108.40.206 - - [04/Aug/2009:08:00:42 -0500] "GET /feed/ HTTP/1.1" 302 - "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
Try any of those "pages" in your browser, both with and without www in the request, and look at the responses in Live HTTP Headers.
Same 302 output.....