Forum Moderators: DixonJones
Some guys use http 302 redirect to redirect their visitors to my site. Worst of them, some of those pages rank higher than my in search engines. Crazy. So I want to set a HTTP 404 or 500 error page for those from redirecting. By doing so, I think search engines will know the redirect URL is bad link so will remove it.
302 Redirects continues to be an issue [webmasterworld.com]
How to Remove Hijacker Page Using Google Removal Tool [webmasterworld.com]
You won't see the other site's 302 in your log. Your log can only capture what happens on your site, and what if volunteered by your visitor's browser.
Your log might catch their referrer, but not that it was a 302 from the referring site, and I'd bet that the referrer value is browser dependent. Give me a day or two and I'll see what I can try here on my site.
Larry
I'd regret to inform you that your ISP is clueless in this matter. As you pointed out, it is difficult for it to know if a visitor has seen a page.
However, the browser knows when it last requested a file in its cache, and when it re-requests that same file instead of just asking for the URL, it actually says "Hey, if this file has been updated since #*$!, give it to me, otherwise just let me know my current copy is still good" - That later case is the '304'.
Hope that helps,
Larry N
Likewise your server generates the 301's that you see in the logs such as from www.yoursite .com/folder to www.yoursite .com/folder.index.html.
Neither the redirectors or bots return referrer information... so the request www.yoursite .com/folder.index.html or www.theirsite .com/go2php?/www.yoursite .com/folder.index.html will look the same either way to you on your server logs as your server will return the the page code 200, a 304 cached page or a 403 or 404 error etc.
I take it that there's no way to see 302s on my access_log files.
A 302 would be returned as a 200, 304 or other number as applicable,
most likely a 200. That's a real shame.
If everyone could easily see incoming 302 redirects, they would be
much more inclined to do something about it. Not everyone is likely
to jump thru hoops to find out if they are being victimized. -Larry
I don't quite follow your thoughts on server return status 302 - Moved Temporarily; Your access log should log any requests to your server, you would have to generate the moved temporarily location header with that status of 302, and your server should log that request and response.
If fact some servers used to respond with a 302 if an incomplete path "http://www.xyz.com" instead of "http://www.xys.com/" was requested. But those days are long gone...
Larry N